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 commands/stahl-g/briefloop/propose-competitorsgit clone --depth 1 https://github.com/Stahl-G/briefloopWrote 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/stahl-g/briefloop/propose-competitors)<a href="https://agentmods.dev/commands/stahl-g/briefloop/propose-competitors"><img src="https://agentmods.dev/badge/commands/stahl-g/briefloop/propose-competitors.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 | $0.00012 | $0.00290 |
| Opus 5 | $0.00006 | $0.00145 |
| Sonnet 5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
propose-competitors 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.
What it actually says
You are recommending competitor candidates for workspace: $ARGUMENTS
Follow this sequence:
-
Read context files:
- $ARGUMENTS/user.md
- $ARGUMENTS/config.yaml
- $ARGUMENTS/competitor_universe.yaml (target entity and any existing entities)
-
Call the market-competitor-planner subagent:
- Provide user.md context (company, industry, market_scope, focus_areas).
- Ask it to recommend 3-8 competitor entities.
- Each candidate must include: entity_id, name, aliases, relation, relevance_reason, market_overlap (geography, product, value_chain), confidence, and approved: false.
-
Write $ARGUMENTS/competitor_candidates.yaml:
- Merge existing approved-but-not-merged candidates (if any).
- Add new recommendations from the planner.
- Do NOT set approved: true for any candidate.
-
Report:
- How many candidates were added.
- Which entities were recommended and why (briefly).
- Remind user to review candidates, set
approved: trueon confirmed ones, then runbriefloop competitors merge --config $ARGUMENTS/config.yaml. - Do not auto-approve or merge candidates.
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 · 33 lines · 12 tokens per session scan A c4b9fbe32303
propose-competitors is a command published in the GitHub repository Stahl-G/briefloop (9 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
usage
Audit pipeline: token spend attributed by phase, task, model, author and time — with cache economics, cost-per-task and a usage trend. Read-only (never mutates the manifest).
krait-review
Re-examine findings killed by the Critic's automatic gates. Catches over-filtering without compromising the main report's zero-FP standard.
report
Produce executive and technical compliance reports.
phase
Audit pipeline: everything a phase has done to it — add one to a plan that already exists, run it end to end (every ready task, parallel where safe, then sign-off), pin which phase the pipeline reaches for first, or cancel one that will not be done. A bare runs it; --dry-run previews the run without mutating.
cost
Produce a reconciled API-equivalent cost estimate for a completed Whats.Going.On. audit.