infisical-dev

v1.1.0

Infisical CLI dev plugin for Agents Store. Complete command-line coverage for secrets management — install & auth, infisical run/secrets/export, dynamic secrets, secret scanning with pre-commit hooks, machine-identity CI/CD auth, self-hosted, and troubleshooting.

Agent Plugins6 Skills

By AGENTS.STORE0 GitHub starsUpdated last week

Directory evidence

Runtimes: Agent Plugins
Parsed components: 6 skill or MCP entries
Source updated: Oct 7, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Get the plugin

$ git clone https://github.com/Agents-Store/agentplugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is infisical-dev/.

This listing currently publishes only the generic Agent Plugins format. Automatic install commands for other clients are not generated yet.

Plugin files

infisical-dev/

├── plugin.json
├── skills/ci-cd-auth/SKILL.md
├── skills/cli-recipes/SKILL.md
├── skills/cli-reference/SKILL.md
├── skills/secret-scanning/SKILL.md
├── skills/setup/SKILL.md
└── skills/troubleshoot/SKILL.md

Included Skills6

ci-cd-authskills/ci-cd-auth/SKILL.md

This skill should be used when the user asks to "use Infisical in CI/CD", "Infisical machine identity", "infisical login universal-auth", "authenticate Infisical without a browser", "Infisical in Docker", "inject secrets in a pipeline", "Infisical Kubernetes/AWS/GCP/Azure auth", or "bootstrap a self-hosted Infisical" — non-interactive Infisical CLI authentication and secret injection for automation.

cli-recipesskills/cli-recipes/SKILL.md

This skill should be used when the user asks about "Infisical run", "infisical secrets", "inject secrets into a process", "Infisical export to .env", "infisical CLI commands", "manage secrets from the terminal", "Infisical folders", or "Infisical dynamic secrets lease" — the everyday Infisical CLI workflows for fetching, setting, injecting, and exporting secrets.

cli-referenceskills/cli-reference/SKILL.md

This skill should be used when the user asks for "Infisical CLI reference", "all Infisical commands", "Infisical CLI flags", "Infisical environment variables", "infisical command list", or needs the full command/flag/env-var reference for the Infisical CLI.

secret-scanningskills/secret-scanning/SKILL.md

This skill should be used when the user asks to "scan for secrets", "Infisical scan", "find leaked secrets in git", "set up a pre-commit secret scan", "infisical scan git-changes", "scan repo for API keys", "add a secret-scanning baseline", or "ignore a false-positive secret" — using the Infisical CLI to detect and prevent committed secrets.

setupskills/setup/SKILL.md

This skill should be used when the user asks to "install Infisical CLI", "set up Infisical CLI", "log in to Infisical", "authenticate Infisical CLI", "verify Infisical is working", "is Infisical CLI working", "point Infisical at self-hosted", or needs to get the Infisical CLI installed, authenticated, and confirmed operational.

troubleshootskills/troubleshoot/SKILL.md

This skill should be used when the user hits "Infisical CLI errors", "Infisical login fails", "Infisical keyring error", "infisical project not found", "Infisical token not working", "Infisical self-hosted connection issues", "infisical run no secrets", or needs to diagnose and fix problems with the Infisical CLI.

Plugin manifests1

infisical-dev/plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "infisical-dev",
  "version": "1.1.0",
  "description": "Infisical CLI dev plugin for Agents Store. Complete command-line coverage for secrets management — install & auth, infisical run/secrets/export, dynamic secrets, secret scanning with pre-commit hooks, machine-identity CI/CD auth, self-hosted, and troubleshooting.",
  "author": {
    "name": "AGENTS.STORE"
  },
  "keywords": [
    "infisical",
    "cli",
    "secrets",
    "secrets-management",
    "secret-scanning",
    "machine-identity",
    "devsecops",
    "ci-cd",
    "dotenv",
    "dev",
    "agents-store"
  ],
  "extensions": {
    "com.anthropic.claude-code": {
      "agents": "./com.anthropic.claude-code/agents/"
    }
  }
}

Browse the “infisical” tag →

infisical-dev

by AGENTS.STORE

Claude Code6 Skills

0Updated last week

infisical-dev

by AGENTS.STORE

Codex6 Skills

0Updated 2 weeks ago

macstack-dev

by AGENTS.STORE

Turns what a client says into documents they can correct, a machine spec an agent can build from, and a work list somebody can pick up. Keeps the macstack/ folder of a project: macstack.json — the standardized business + technical stack specification, always English — and the six client documents it is written from. OVERVIEW says what the product is and who it is for; USER-CASES carries each case with its UX bar and an addressable acceptance list; UX-UI states what each screen shows and what must never appear on it; AUTOMATION is the trigger -> task -> workflow -> role model; HANDBOOK is how a person actually uses the thing; OPEN-QUESTIONS splits what the client owes from what the team deferred. v3 makes those six pure markdown — headings and bullet lists, nothing else. No YAML blocks, no tables, no change-log sections: the only machine markup is an HTML comment the reader never sees, pointing each entity at its place in the spec. A client can edit the document in any editor and hand it back. Around them: an immutable inbox for anything a client sends, a gated delta/rulings loop that merges it, generated requirements, architecture, test cases and index that carry every id the client documents carry, an append-only ledger with one row per edit and per client comment, tasks reconciled with the team's own tracker, and a review package that shows each statement with its own history and reads the client's answers back into the ledger. Eight commands, one job each — including one that reconciles the whole folder against the source tree in a direction you have to declare: the code is master and every document is corrected through a gate that never silently overrules an answer the client gave, or the documents are master and the gaps become tasks. Every edit is journalled, every finished task sweeps the client documents and not only the generated ones, task statuses move to what the audit actually found — closing what is built and reopening what is not — and every document carries the date it was last checked against the code, so a document that reads perfectly cannot quietly describe a system that no longer exists.

Claude Code17 Skills

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[infisical-dev on Agent Plugins Marketplace](https://pluginsmp.com/plugins/infisical-dev-2)

Directory evidence

Get the plugin

Plugin files

Included Skills6

Plugin manifests1

Related plugins

For maintainers

Related plugins