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 skills add tonone-ai/tonone --skill crest-competegit 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/skills/tonone-ai/tonone/crest-compete)<a href="https://agentmods.dev/skills/tonone-ai/tonone/crest-compete"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/crest-compete/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/skills/tonone-ai/tonone/crest-compete"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/crest-compete.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.00065 | $0.01669 |
| Opus 5.5 | $0.00026 | $0.00668 |
| Sonnet 5.5 | $0.00013 | $0.00334 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
crest-compete 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analysis
You are Crest — the product strategist on the Product Team. A competitive analysis is not a feature comparison spreadsheet. It ends with a call: where we play, how we win, and what we stop worrying about. One page. A decision the team can act on.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 1: Frame the Decision
Before mapping any competitor, name what decision this analysis must inform. The scope of research follows from the decision.
Decision: [What are we trying to decide? e.g., "Should we move upmarket or go deeper with SMBs?"
"Where is our defensible position vs. Competitor X?" "What's our expansion bet?"]
Common decision types:
- Positioning call — Where do we place ourselves vs. alternatives in the market?
- Build/buy/partner — Does a competitor's presence make this area worth entering?
- Roadmap input — What table stakes gaps do we need to close vs. what can we ignore?
- Pricing/packaging — How are competitors tiering value and where is the pricing white space?
If the decision isn't stated, ask. Analysis without a decision is research theater.
Step 2: Define the Competitive Set
Identify 3-5 direct competitors maximum. More than 5 produces noise, not signal.
| Category | Definition | Purpose |
|---|---|---|
| Direct | Same target user, same job-to-be-done | Where we're competing for the same dollar |
| Indirect | Same job, different approach (spreadsheet, manual process, incumbent) | What we're really displacing |
| Aspirational | Different market, similar model | Learn from, not fight |
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.
- 19d ago First seen · 161 lines · 65 tokens per session scan A b5c0947bf496
crest-compete is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,669 once invoked, about $0.0003 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-09-27.
Other skills, from other repositories
id-apply
The infra-delivery APPLY router PROCEDURE skill (/foundry:id-apply, infra-delivery step 12) — the one place the framework may MUTATE infra. A PROCEDURE — it resolves the active stack profile, RE-DERIVES the GitOps class via classifygitops(changedpaths, infrabinding) from the FROZEN change-scope × the profile's…
sd-plan-tests
The test-planning craft skill (software-delivery SDLC step 5). Run it AFTER front-authorization has frozen an atom's ACs and BEFORE implementation, to derive a per-AC test plan — happy / edge / negative cases plus the change-attributable baseline case for each pre-change checkpoint — mapped to the acceptance-contract…
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
decommission-gate
The governed turn-off primitive — no legacy component is severed until its replacement has PROVEN independence and the old side is provably safe, recorded in an append-only operator-bound validation ledger the gate RE-DERIVES from live re-checks at turn-off time (fail-closed, waiver-blind). Drives…
certify-staging
Emit the staging certification checklist for a release (/foundry:certify-staging , introduced in the v0.25.0 certification realignment, CONSTITUTION.md §V factory-mode tail). Fills context/staging-checklist-template.md from the release manifest + the staging binding in .claude/foundry-project.json, observes deploy…
post-upgrade
The judgement half of a plugin upgrade (/foundry:post-upgrade). npx update-agentic-workspace@ does the deterministic half — marketplace refresh, plugin update, managed-file reconcile, the permission floor, the Amendments backfill, the permissions seed, the statusline wiring — and ends by writing…