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/arc-mcp/arc-1/update-competitor-trackergit clone --depth 1 https://github.com/arc-mcp/arc-1Wrote 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/arc-mcp/arc-1/update-competitor-tracker)<a href="https://agentmods.dev/commands/arc-mcp/arc-1/update-competitor-tracker"><img src="https://agentmods.dev/badge/commands/arc-mcp/arc-1/update-competitor-tracker.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.00000 | $0.01486 |
| Opus 5 | $0.00000 | $0.00743 |
| Sonnet 5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
update-competitor-tracker 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 5d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Competitor Commit & Issue Trackers
Fetch new commits and issues from all tracked repos, evaluate relevance to ARC-1, and update all tracking documents.
Repos to Track
| Repo | Tracker Dir | Comparison Doc | Purpose |
|---|---|---|---|
fr0ster/mcp-abap-adt |
docs/compare/fr0ster/ |
docs/compare/05-fr0ster-mcp-abap-adt.md |
Competitor analysis |
oisee/vibing-steampunk |
docs/compare/vibing-steampunk/ |
docs/compare/01-vibing-steampunk.md |
Competitor analysis |
marcellourbani/abap-adt-api |
docs/compare/abap-adt-api/ |
docs/compare/02-mcp-abap-abap-adt-api.md |
API implementation reference |
Instructions
Run all repos in sequence. For each repo, follow steps 1–4, then do step 5 (cross-repo updates) once at the end.
1. Fetch New Commits
Read docs/compare/<repo>/commits.json and note the lastCheckedSha.
Fetch commits newer than that SHA:
/opt/homebrew/bin/gh api "repos/<owner>/<repo>/commits?per_page=100" --jq '.[] | "\(.sha[:7])|\(.commit.author.date[:10])|\(.commit.message | split("\n")[0])"'
Stop when you reach the lastCheckedSha. If there are no new commits, skip to step 3.
2. Triage New Commits
For each new commit:
-
Auto-skip these prefixes — no evaluation needed:
chore:,docs:,ci:,test:,style:,refactor:,Merge,release:, version bumps
-
Evaluate
feat:and significantfix:commits:- Check if ARC-1 already has this feature/fix
- Assess relevance: does ARC-1's architecture need this?
- Assign priority:
high(implement),medium(consider),low(defer),skip(not relevant) - Write a decision:
implement,consider-future,verify,defer,skip,no-action,not-applicable,keep-current,covered-by-X
-
Add to commits.json:
- Insert new commits into the correct release group (or create a new release group)
- Update
lastCheckedShato the newest commit - Update stats counters
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.
- 5d ago First seen · 134 lines · 0 tokens per session scan A 4ff9a15ebacb
update-competitor-tracker is a command published in the GitHub repository arc-mcp/arc-1 (174 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,486 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.