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/codeready-toolchain/tarsy/analyze-onlygit clone --depth 1 https://github.com/codeready-toolchain/tarsyWrote 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/codeready-toolchain/tarsy/analyze-only)<a href="https://agentmods.dev/commands/codeready-toolchain/tarsy/analyze-only"><img src="https://agentmods.dev/badge/commands/codeready-toolchain/tarsy/analyze-only.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00216 |
| Opus 5 | $0.00000 | $0.00108 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
analyze-only 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 5d ago.
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
Comprehensive Analysis Only
DO NOT CHANGE ANY CODE. Perform analysis and provide recommendations only.
When the user later asks to implement (e.g., "do it", "implement this", "proceed"), then make the changes directly. Don't ask for confirmation, but DO ask clarifying questions if there's genuine uncertainty about what or how to implement.
Analysis Guidelines
Perform a thorough investigation of the requested topic, codebase area, or problem:
Investigation
- Read relevant files and understand existing implementations
- Trace data flow and dependencies
- Identify patterns and architectural decisions
- Look for related functionality across the codebase
- Use web search or documentation if encountering unfamiliar technologies
Findings Report
- Summarize current state and implementation
- Describe discovered patterns and approaches
- Highlight potential issues or concerns
- Suggest possible solutions or next steps with implementation approach
Restrictions
- No code changes
- No file modifications (including documentation files)
- Analysis and recommendations only
Present findings clearly with references to specific files and line numbers where relevant.
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.
- 5d ago First seen · 32 lines · 0 tokens per session scan A 76f3fcd346b1
analyze-only is a command published in the GitHub repository codeready-toolchain/tarsy (10 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 216 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
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
status
Display project status, active tracks, and next actions.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.