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.
git clone --depth 1 https://github.com/SunflowersLwtech/covateWrote 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/sunflowerslwtech/covate/review-record)<a href="https://agentmods.dev/commands/sunflowerslwtech/covate/review-record"><img src="https://agentmods.dev/badge/commands/sunflowerslwtech/covate/review-record/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sunflowerslwtech/covate/review-record"><img src="https://agentmods.dev/badge/commands/sunflowerslwtech/covate/review-record.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00067 |
| Opus 5.5 | $0.00005 | $0.00027 |
| Sonnet 5.5 | $0.00003 | $0.00013 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
review-record 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
Follow the "Score the answers" steps of the covate-review skill for the page $ARGUMENTS,
including its last step, showing where things stand.
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 · 10 lines · 13 tokens per session scan A 7cbe6f34c70b
review-record is a command published in the GitHub repository SunflowersLwtech/covate (8 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 67 once invoked, about $0.0001 per session on Opus 5.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-10-27.
Other commands, from other repositories
is-not-duplicated
please investigate the codebase based on your changes - do we have code duplication? After analysis, write updates to DUPLICATIONREPORT.md with the results. Keep in mind that other agents could keep their records, so you need to check the document first, decided to update or add new information.
code-patterns
Catálogo de patterns del proyecto con ejemplos del propio código del equipo.
docs
sentry docs answers include inline links and a Sources section containing the Sentry documentation pages used to answer the question. Use sentry docs list to search the documentation index instead; --limit restricts the number of results and --json returns structured output.
start-11-4.es
Leccion 11-4: Llamar a AI CLI desde GitHub Actions!
review
Comprehensive code review for blz changes.
show_diff
Call the showdiff MCP tool to show me a side-by-side visual diff (it returns an image in the chat). If I passed a checkpoint sha in $ARGUMENTS, diff that checkpoint; otherwise show my current uncommitted changes.