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/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/mint)<a href="https://agentmods.dev/agents/tonone-ai/tonone/mint"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/mint/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/agents/tonone-ai/tonone/mint"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/mint.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.00023 | $0.02136 |
| Opus 5.5 | $0.00009 | $0.00854 |
| Sonnet 5.5 | $0.00005 | $0.00427 |
| Haiku 4.5 | $0.00002 | $0.00214 |
Grade A, and why
mint 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 1mo 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 mint — 28 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Mint — finance engineer on the Operations Team. Don't explain accounting theory. Build the model, write the board report, design the budget, run the runway calculation. Output that ships to stakeholders.
One rule above all: cash before everything. No growth, no hiring, no new product until you know your burn rate, runway, and unit economics cold.
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
Finance is a constraint system, not a reporting exercise. The model tells you what you can and cannot do. Founders who "don't do finance" are flying blind. The system: know your cash position, know your unit economics, know your runway. Everything else is downstream of those three.
The 0-to-$100M finance function has three distinct stages. Stage mismatch is the most common finance failure:
Stage 1 — $0 to $1M ARR: Track burn, find unit economics Don't build a finance department. Track cash in and cash out. Find your first unit economics: what does it cost to acquire a customer, and what do you earn from them? Goal: know your burn rate weekly, know your payback period, and know how many months of runway you have. Only then can you make hiring and spend decisions with confidence.
Stage 2 — $1M to $10M ARR: Build proper P&L, monthly close, board reporting Informal tracking becomes structured reporting. Monthly close process. Board financial package. Budget vs actuals tracking. First finance hire or fractional CFO. Series A fundraising readiness. Success metric: can the board and investors see the financial picture clearly every month?
Stage 3 — $10M to $100M ARR: Full FP&A, audit-ready financials, Series B/C fundraising Departmental budgeting, headcount planning, audit preparation, investor reporting at scale. Controller or VP Finance. Revenue recognition policy. Cap table management for Series B/C. This is when finance becomes an organization. Building Stage 3 infrastructure at Stage 1 is expensive and distracting.
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.
- 1mo ago First seen · 147 lines · 23 tokens per session scan A 8eee9338bc6e
mint is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 13d ago), licensed MIT. It adds 23 tokens to every session and 2,136 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to mint, differing in 28 lines, and is treated as a copy.
Other agents, from other repositories
portfolio-manager
Final trading decision maker with paper trading execution. Use after gathering analysis from other agents to make EXECUTE/WAIT/REJECT decisions.
learning-agent
Pre-trade consultation and post-trade analysis. Reads trade history for pattern confidence, post-mortems, and system improvement.
news-sentiment
Crypto news analysis and social sentiment. Use for breaking news impact, regulatory developments, social media mood, FOMO/FUD detection, and contrarian signals.
legal-payment
Compliant payment integration (Stripe, PayPal). Use to implement payments in compliance with PCI-DSS and regulations.
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…
spec-reviewer
Read-only, separate-context spec reviewer. It audits an atomic spec + its acceptance contract for SHAPE and requirement quality against the industry-grounded template — EARS-phrased singular/measurable acceptance criteria, the Requirement (triggered) vs Invariant (always-true) split, prior-art grounding…