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/kylepelham/DriftWrote 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/kylepelham/drift/issues)<a href="https://agentmods.dev/commands/kylepelham/drift/issues"><img src="https://agentmods.dev/badge/commands/kylepelham/drift/issues/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/kylepelham/drift/issues"><img src="https://agentmods.dev/badge/commands/kylepelham/drift/issues.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.00006 | $0.00120 |
| Opus 5 | $0.00003 | $0.00060 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
issues 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 3d 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.
This is a copy
100% identical to issues — 0 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
Search through existing issues in anomalyco/opencode using the gh cli to find issues matching this query:
$ARGUMENTS
Consider:
- Similar titles or descriptions
- Same error messages or symptoms
- Related functionality or components
- Similar feature requests
Please list any matching issues with:
- Issue number and title
- Brief explanation of why it matches the query
- Link to the issue
If no clear matches are found, say so.
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.
- 3d ago First seen · 24 lines · 6 tokens per session scan A cc8fd1121ba2
issues is a command published in the GitHub repository kylepelham/Drift (20 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 120 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to issues, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
adoption-track
Tracking de adopción — comandos usados por rol, curva de aprendizaje, puntos de fricción.
ai-exposure-audit
Auditoría de exposición IA por rol — observed exposure, riesgo de desplazamiento, reskilling.
adoption-sandbox
Entorno seguro de práctica — experimentar con Savia sin miedo a errores.
backlog-groom
Grooming asistido — detectar items obsoletos, duplicados, sin criterios de aceptación.
bias-check
Auditoría contrafactual de sesgos en asignaciones y comunicaciones del sprint.
confluence-publish
Publicar documentación del proyecto en Confluence. Convierte markdown a formato Confluence y crea/actualiza páginas en el espacio del proyecto.