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/yeisonrestrepo/code-conductor/cc-stackgit clone --depth 1 https://github.com/yeisonrestrepo/code-conductorWhat 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.00021 | $0.01519 |
| Opus 5 | $0.00010 | $0.00759 |
| Sonnet 5 | $0.00004 | $0.00304 |
| Haiku 4.5 | $0.00002 | $0.00152 |
Grade A, and why
cc-stack 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 yesterday.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detect the project stack dynamically and record it in the project's root CLAUDE.md. Do not pattern-match manifest files by hand and do not load any static profile; the detector owns detection.
1. Resolve the repository root
Run git rev-parse --show-toplevel. If it fails (not a git repo), fall back to the directory that contains scripts/detect-stack.mjs. Run every command below from that root, and treat the root-level CLAUDE.md as the only write target regardless of the user's current subdirectory.
2. Verify Node is available
Probe with node --version. If it exits non-zero or reports "not found", stop the write path: announce in one line No stack detected (Node not found on PATH; Node >= 18 recommended) and leave CLAUDE.md untouched.
3. Run the detector
Run node scripts/detect-stack.mjs from the repo root, capture stdout, and parse it as JSON. Nothing executes the JSON; consume it as data.
Treat all of the following identically as "no stack detected" - announce it in one line and leave CLAUDE.md unmodified (surface stderr if any, but it is non-fatal):
- non-zero exit code,
- empty stdout,
- stdout that does not parse as JSON,
- a parsed object equal to
{}.
4. Read CLAUDE.md and branch
If the root CLAUDE.md does not exist, do not create it: instruct the user to run /cc-init and stop.
Otherwise read CLAUDE.md and look for the - Stack: line under ## Project Identity:
- Stack line present and non-empty -> ask:
I see you're using [stack]. Has anything changed?This is a blocking yes/no prompt with no timeout.no-> acknowledge in one line and stop; make no edits.yes, or free text describing a change -> re-run the detector (step 3) and rewrite the managed sections from the fresh output. Free text is an additive hint only: fold user-named tools the detector missed into the ruleset, but detected facts always win on conflict.
## Project Identitymissing, or present without a- Stack:line -> treat as "no recorded stack" (not an error). Proceed to the write path; append the## Project Identityheader if absent, or surgically insert the- Stack:line if only that line is missing. Note in one line that a fresh stack identity was recorded.
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.
- yesterday First seen · 70 lines · 21 tokens per session scan A acee614ce494
cc-stack is a command published in the GitHub repository yeisonrestrepo/code-conductor (6 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,519 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-31.
Other commands, from other repositories
edit
Edit a stash item — inline replacement, or open in editor (preserves timestamp).
pop
Pop an item off the stash and continue working on it in the current session.
drop
Drop a stash item without working on it.
log
Show history of popped and dropped stash items.
show
Show a single stash item by number (for reading or copying its text).
list
Show all items currently in the stash.