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.
git clone --depth 1 https://github.com/AgriciDaniel/ace-claude-codeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/agricidaniel/ace-claude-code/config)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/config"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/config"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00010 | $0.01017 |
| Opus 5.5 | $0.00004 | $0.00407 |
| Sonnet 5.5 | $0.00002 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
ace:config 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Without arguments: display current configuration. With arguments: modify specific settings with validation.
Modifiable settings:
- workflow.mode (interactive | yolo)
- qualityGates.typescript.enabled (true | false)
- qualityGates.lint.enabled (true | false)
- qualityGates.build.enabled (true | false)
- qualityGates.test.enabled (true | false)
- qualityGates.*.command (string)
- git.enabled (true | false)
- git.autoInit (true | false)
- git.perTaskCommits (true | false)
- projectType.current (frontend | backend | fullstack | automation | agentic | library | monorepo | custom)
- orchestration.maxTeamLeads (1-5)
- orchestration.maxTasksPerPlan (1-10)
1. Parse Arguments
if $ARGUMENTS is empty:
MODE = "view"
else:
Parse: setting.path value
Example: "workflow.mode yolo"
MODE = "modify"
2. View Mode (No Arguments)
Read config.json and display:
+==============================================================+
| ACE CONFIGURATION |
+==============================================================+
Orchestration:
Mode: [parallel]
Max Team Leads: [3]
Max Tasks/Plan: [3]
Workflow:
Mode: [interactive] (interactive | yolo)
Quality Gates:
TypeScript: [enabled] - npx tsc --noEmit
Lint: [disabled] - npm run lint
Build: [enabled] - npm run build
Test: [disabled] - npm run test
Git:
Enabled: [true]
Auto Init: [true]
Per-Task Commits: [true]
Project Type:
Current: [agentic]
+==============================================================+
Modify: /ace:config <setting.path> <value>
Example: /ace:config workflow.mode yolo
+==============================================================+
3. Modify Mode (With Arguments)
3.1 Validate Setting Path
validPaths = [
"workflow.mode",
"qualityGates.typescript.enabled",
"qualityGates.lint.enabled",
"qualityGates.build.enabled",
"qualityGates.test.enabled",
"qualityGates.typescript.command",
"qualityGates.lint.command",
"qualityGates.build.command",
"qualityGates.test.command",
"git.enabled",
"git.autoInit",
"git.perTaskCommits",
"projectType.current",
"orchestration.maxTeamLeads",
"orchestration.maxTasksPerPlan"
]
if setting.path not in validPaths:
Display error: "Invalid setting path: [path]"
List valid paths
EXIT
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.
- 1mo ago First seen · 187 lines · 10 tokens per session scan A 00e80d89a8ef
ace:config is a command published in the GitHub repository AgriciDaniel/ace-claude-code (27 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,017 once invoked, about $0.0000 per session on Opus 5.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
fix-issue
Analyze and fix a GitHub issue.
beads-onboard
Run the interactive beads-onboard interview in the current project to generate beads conventions (AGENTS.md translation matrix, labels.md, reference.md, starter formula, pre-seeded bd remember entries).
bmad-create-story
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".
bmad-sprint-planning
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan".
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
gpd:record-insight
Record a project-specific learning or pattern to the insights ledger.