Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add anilcancakir/claude-code/plugin install acWrote 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/anilcancakir/claude-code/install)<a href="https://agentmods.dev/commands/anilcancakir/claude-code/install"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code/install/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/anilcancakir/claude-code/install"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code/install.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.00035 | $0.13435 |
| Opus 5.5 | $0.00014 | $0.05374 |
| Sonnet 5.5 | $0.00007 | $0.02687 |
| Haiku 4.5 | $0.00003 | $0.01344 |
Grade D, and why
install scanned grade D with 2 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**CANNOT**: Hand-write `my-coding` or `my-language` SKILL.md content; that is `ac:skill-creator`'s job. Blind-overwrite `~/.claude/CLAUDE.md` or `~/.claude/settings.json`; both go through a backup plus a gate. Write sett Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- When `LEGACY_MY_WORKFLOW` was found, say `rm -rf ~/.claude/skills/my-workflow` removes the now-duplicated copy. How it starts
The opening of the file, as written. The whole thing — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ac:install
Tunes your user-scope environment so the ac workflow replaces the matching Claude Code built-ins. Safe defaults apply silently; anything that loosens a gate or touches a secret is opt-in.
Request: $ARGUMENTS
Precondition: the ac plugin is already installed and loaded. This command does not bootstrap the install and never calls /plugin marketplace add or /plugin install. It writes only under ~/.claude/, and only the files each phase names; the one exception is the wrapper line 3d adds to a shell rc file, and only after the operator says yes.
Phase 0: Identity, arguments, preflight, languages
You are the /ac:install orchestrator. You interview the operator, delegate skill authoring to ac:skill-creator, and write user-scope config behind explicit gates.
CAN: Use Read, Write, Edit, Bash, AskUserQuestion. Invoke ac:skill-creator through the Skill tool. Probe the ac MCP server with mcp__plugin_ac_ac__resolve-library. Write the .proposed sidecar, the .bak-ac-install backups, the ~/.claude/ac-install.json answer record, and the stable rules copy at ~/.claude/ac/working-rules.md.
CANNOT: Hand-write my-coding or my-language SKILL.md content; that is ac:skill-creator's job. Blind-overwrite ~/.claude/CLAUDE.md or ~/.claude/settings.json; both go through a backup plus a gate. Write settings keys from memory; the Phase 4 reference is the only source. Edit anything outside ~/.claude/, apart from the 3d wrapper edit to a shell rc file after an explicit yes. Widen an allow rule past the literal server segment (mcp__plugin_ac_ac__*, never mcp__*).
MUST: Honour every flag from 0a for the whole run. Under --dry-run, render every planned change and call no Write or Edit. Back up each file before rewriting it. Leave an existing skill alone unless the operator picks Recreate. Read the Phase 3 template and the Phase 4 reference rather than reproducing either from this body: both have drifted from a restated copy before, and a stale copy fails silently.
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.
- today Changed · +99 lines 24ed48e5760b
- 15d ago Changed · +39 lines · +6 tokens per session 7b79d1343f52
- 22d ago Changed · +2 lines · -36 tokens per session scan B → D 5b083b3deb31
- 1mo ago Changed · -58 lines · +65 tokens per session scan D → B 838a9503222b
- 1mo ago First seen · 380 lines · 0 tokens per session scan D ca7601b27999
install is a command published in the GitHub repository anilcancakir/claude-code (3 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 13,435 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
ccc-orchestrate
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
ralph-help
Explain Ralph Loop plugin and available commands.
design
A command that turns an existing plan into a detailed technical design for building the feature.