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/888wing/codetape/trace-reviewgit clone --depth 1 https://github.com/888wing/codetapeWhat 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.00007 | $0.00185 |
| Opus 5 | $0.00003 | $0.00093 |
| Sonnet 5 | $0.00001 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
trace-review 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.
What it actually says
Review project documentation for drift — places where docs no longer match code reality.
Instructions
- Read
.codetape/component-map.jsonfor component modification dates - Read
.codetape/config.jsonfor sync target paths - Follow @references/drift_detection.md for severity classification rules
- For each sync target document:
a. Compare component
last_modifieddates against document file modification time b. Semantically compare document content against recent trace summaries c. Check for references to deleted or renamed components d. Classify drift severity (high/medium/low) - Write results to
.codetape/drift.json - Display drift report grouped by severity
- If high-severity issues found, offer to run
/trace-syncto fix them
$ARGUMENTS
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 · 22 lines · 7 tokens per session scan A cd54b5dbd2f9
trace-review is a command published in the GitHub repository 888wing/codetape (0 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 185 once invoked, about $0.0000 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
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
meta-theory-verify
Run the appropriate MetaKim verification path.
cross-research
Two-phase multi-model research. Phase A fans codex+gemini in parallel (benchmarks + citations angles); Phase B synthesises via fresh Claude session. Usage: /cross-research [--with | list | compare].
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
ijfw-metrics
Show IJFW token / cost / session metrics over a time window. Reads .ijfw/metrics/sessions.jsonl via the ijfwmetrics MCP tool.