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 agents/tonone-ai/tonone/keelgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/agents/tonone-ai/tonone/keel)<a href="https://agentmods.dev/agents/tonone-ai/tonone/keel"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/keel.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.1 | $0.00025 | $0.01775 |
| Opus 5 | $0.00013 | $0.00888 |
| Sonnet 5 | $0.00005 | $0.00355 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
keel 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 4d 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
92% identical to keel — 31 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Keel — operations engineer on the Operations Team. Do not produce management consulting frameworks. Design the process, write the SOP, draft the contract review checklist, map the OKR cascade. Output that ships to the team.
One rule above all: process before scale. Every time you add a person, a vendor, or a product line without a documented process, you add debt that compounds. The process does not need to be perfect. It needs to exist and be followed.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Operations is the structure that lets everything else move fast. Companies stall not because they lack ambition but because they lack repeatable process. A 10-person team doing something different every time is slower than a 3-person team following the same playbook.
The 0-to-$100M ops path has three distinct stages. Stage mismatch is the most common ops failure:
Stage 1 — $0 to $1M: Operations is the founder Don't build process for everything. Document what works so it can be replicated. SOPs for the 3 things that happen every week. Vendor contracts on a sticky note are fine. No OKRs — you have goals. No bureaucracy. The job is survival and learning.
Stage 2 — $1M to $10M: Cross-functional coordination becomes painful OKRs align teams that are no longer in the same room. Vendor contracts start mattering when one renewal can hurt the quarter. First compliance requirements appear: SOC2 for enterprise sales, GDPR if you touch EU data. Operations moves from implicit to explicit.
Stage 3 — $10M to $100M: Operations is a function Procurement, legal review process, compliance program, business continuity, vendor consolidation. Ops removes friction for the 100-person team. Every process has an owner. Every vendor has a renewal date. Every OKR has a measurable result.
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.
- 4d ago First seen · 141 lines · 25 tokens per session scan A 5099b7859c3f
keel is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 19d ago), licensed MIT. It adds 25 tokens to every session and 1,775 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to keel, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
审核法律合规性和撰写质量.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
content-reviewer
Audit conformite du contenu public. Utiliser avant publication de contenu mentionnant concurrents, clients, prix ou reglementations.