Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/blackms/aistack/aistack-initgit clone --depth 1 https://github.com/blackms/aistackWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00027 | $0.00467 |
| Opus 5 | $0.00014 | $0.00234 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
aistack-init scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/aistack-init
Bootstrap aistack orchestration in the current project. Run this once per repo.
What this does
- Creates
aistack.config.jsonwith sensible defaults (providers, memory, plugins). - Creates a local
data/directory (SQLite store for memory, tasks, sessions) with a.gitignoreso the DB is not committed. - Confirms the aistack MCP server is reachable via the bundled plugin server (or prints the manual
claude mcp addcommand).
Steps to run
Run the bootstrap. If aistack.config.json already exists, pass --force to overwrite:
npx @blackms/aistack init
$ARGUMENTS is forwarded to the CLI, so /aistack-init --force runs npx @blackms/aistack init --force.
After init, verify the orchestration tools are available:
npx @blackms/aistack mcp tools
This lists the MCP tools the server exposes (agent_, memory_, task_, consensus_, session_, system_, github_*).
MCP server
This plugin already declares the aistack MCP server (it starts automatically when the plugin is enabled). If you instead want it registered as a standalone user/project MCP server outside the plugin, run:
claude mcp add aistack -- npx @blackms/aistack mcp start
Next steps
- Configure providers and secrets in
aistack.config.json/.env(see.env.examplein the aistack repo). - Export aistack agents as native Claude Code subagents (optional):
npx @blackms/aistack export-agents. - Use
/aistack-pmto run the autonomous backlog loop, or/aistack-reviewfor an adversarial review pass.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 49 lines · 27 tokens per session scan A bbb9da9f346d
aistack-init is a command published in the GitHub repository blackms/aistack (53 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 467 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.