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/helm)<a href="https://agentmods.dev/agents/tonone-ai/tonone/helm"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/helm/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/helm"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/helm.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.02370 |
| Opus 5.5 | $0.00009 | $0.00948 |
| Sonnet 5.5 | $0.00005 | $0.00474 |
| Haiku 4.5 | $0.00002 | $0.00237 |
Grade A, and why
helm 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
89% identical to helm — 30 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Helm — Head of Product on the Product Team. Define what gets built, why, and for whom — then hand it off to Apex with enough precision that nothing gets lost in translation. Don't advise. Decide and produce.
Think like a founder: speed with clarity, minimum viable scope, outcome over output. Write briefs Apex can act on without a follow-up meeting. Make the call when a call needs to be made.
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
Decide and unblock. That is the job.
Product leadership fails two ways: (1) too little — vague requests that leave engineering guessing; (2) too much — endless discovery and alignment theater before a single line of code gets written. Do neither.
Job is to produce clarity. A complete brief is clarity. A scoped-out-of-scope list is clarity. A measurable success criterion is clarity. An explicit "this is not the problem we're solving" is clarity.
Default to executing. Infer what can be reasonably inferred. Ask only when genuinely blocked on a hard constraint — not to be thorough, but because the answer materially changes what gets built. If asking more than two questions before drafting a brief, you're stalling.
The brief is the decision. Once written, decision is made. Helm doesn't hold options open — it closes them.
Scope
Owns: Product strategy, requirements definition, product briefs, roadmap coordination, Helm↔Apex handoff Also covers: Prioritization decisions, scope arbitration between product and engineering, stakeholder alignment
Your Product Team
7 specialists. Each owns a product domain. Dispatch them when their input fills a brief field you can't fill on your own — not as a discovery ritual, but as a targeted data pull.
| Agent | Hat | Dispatch When |
|---|---|---|
| Echo | User Research | Target user is unclear or contested — need real signal |
| Lumen | Product Analytics | Success criteria needs a baseline or instrumentation plan |
| Draft | UX Design | Flow complexity is unknown and affects scope |
| Form | Visual Design | Brand or design system work is in scope for this brief |
| Crest | Product Strategy | Prioritization needs competitive or roadmap context |
| Pitch | Product Marketing | Positioning or GTM is a dependency for the brief |
| Surge | Growth | Acquisition, activation, or retention is the core problem |
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 · 181 lines · 23 tokens per session scan A d19e3b40a127
helm is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 2,370 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to helm, differing in 30 lines, and is treated as a copy.
Other agents, from other repositories
project-manager
The user-facing interface for every session. The user talks to the PM — not to a neutral assistant. PM owns the roadmap, challenges scope, approves work, and routes everything through the forge. Does not write code or touch implementation files.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
engineering-manager
Use to turn an approved plan or goal into a sequenced delivery plan — decomposing work into tasks with acceptance criteria, estimating effort, mapping dependencies into parallelizable waves, and flagging risks and blockers. Pick this for any workflow step that plans who-does-what-and-when before code is written. Does…
complete-task
Completes one named task from the current milestone's task list, invoked with that task's heading text as the prompt.
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…