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/dr-code/tessera/reviewgit clone --depth 1 https://github.com/dr-code/tesseraWhat 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.00011 | $0.00500 |
| Opus 5 | $0.00005 | $0.00250 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
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.
This is a copy
88% identical to review — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Code Review
Review the current changes for:
Branch Check
Verify the current branch context:
git branch --show-current
- If on
mainormasterandauto_branch = trueinclaude-mastery-project.conf: warn — "You're reviewing changes directly on main. Next time, start work on a feature branch." - Report which branch is being reviewed in the output header
- Review is read-only so no auto-branch is created, but the warning reminds the user for future commands
Context
- Current diff: !
git diff HEAD - Staged changes: !
git diff --cached
Review Checklist
- Security — OWASP Top 10, no secrets in code, proper input validation
- Types — No
any, proper null handling, explicit return types - Error Handling — No swallowed errors, proper logging, user-friendly messages
- Performance — No N+1 queries, no memory leaks, proper pagination
- Testing — New code has tests, tests have explicit assertions
- Database — Using StrictDB directly, no raw driver imports
- API Versioning — All endpoints use
/api/v1/prefix
RuleCatch Report
After completing the manual review, query RuleCatch for automated violations on the changed files:
- If the RuleCatch MCP server is available: query for violations on the files in the current diff
- Include results in a dedicated section of the review output (see format below)
- This catches pattern-based violations the manual review might miss
- If no MCP available: suggest — "Ask
RuleCatch, what violations happened today?for automated checks"
Output Format
For each issue found:
- File: path/to/file.ts:line
- Severity: 🔴 Critical | 🟡 Warning | 🔵 Info
- Issue: Description
- Fix: Suggested change
RuleCatch Violations
| File | Rule | Severity | Details |
|---|---|---|---|
| ... | ... | ... | ... |
If no RuleCatch violations: "RuleCatch: No violations detected"
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 · 60 lines · 11 tokens per session scan A 99af7f221f65
review is a command published in the GitHub repository dr-code/tessera (1 stars, last pushed 21d ago), licensed MIT. It adds 11 tokens to every session and 500 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to review, differing in 2 lines, and is treated as a copy.
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.