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/secondlifes/code-intel/reviewgit clone --depth 1 https://github.com/SecondLifes/code-intelWhat 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.00000 | $0.00288 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
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
project:review
project:review
Please review the current diffs (git diff and git diff --cached) against this project's coding standards from .claude/CLAUDE.md and the appropriate rules within .claude/rules/ (generated from the canonical .agents/rules/). Structure the review around this checklist: correctness, security, performance, SOLID, resource/memory management, naming, tests, and confirm at minimum that:
- Naming conventions (
snake_case/PascalCase/UPPER_SNAKE_CASE,*_routes.py/*_svc.pysuffixes) are respected. - Routes stay thin — no business logic leaked into a
*_routes.pyhandler instead of its matching*_svc.py. - No new MCP tool uses raw
mcp.tool()instead of this project's@tooldecorator (which auto-generates the REST paritytest_api.py::test_mcp_rest_parityverifies). - No reindex/collection-mutation change bypasses the stage-then-atomic-alias-swap pattern.
- Resource/memory leaks are unlikely with the new changes.
- Qdrant/FastAPI/Ollama-specific constraints are respected — dependency pin discipline, and route handlers left as plain
def(this repo's consistent convention; don't convert toasync defwithout a real, measured reason).
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 · 12 lines · 0 tokens per session scan A 1145d50acb0f
review is a command published in the GitHub repository SecondLifes/code-intel (2 stars, last pushed 21d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 288 tokens. 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.