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/compare-projectsgit 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/compare-projects)<a href="https://agentmods.dev/commands/arc-mcp/arc-1/compare-projects"><img src="https://agentmods.dev/badge/commands/arc-mcp/arc-1/compare-projects.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.00734 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
compare-projects 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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compare Projects
Evaluate all competing SAP ADT/MCP projects against ARC-1 for new features, bug fixes, and patterns to adopt.
Instructions
For each project in the docs/compare/ folder, perform the following checks:
1. Check Recent Activity
For each repository, fetch the latest commits and releases:
- https://github.com/oisee/vibing-steampunk (upstream Go)
- https://github.com/mario-andreschak/mcp-abap-abap-adt-api (abap-adt-api wrapper)
- https://github.com/mario-andreschak/mcp-abap-adt (read-only)
- https://github.com/aws-solutions-library-samples/guidance-for-deploying-sap-abap-accelerator-for-amazon-q-developer (AWS)
- https://github.com/fr0ster/mcp-abap-adt (monorepo, advanced auth)
- https://github.com/lemaiwo/btp-sap-odata-to-mcp-server (OData bridge)
- https://github.com/DassianInc/dassian-adt (elicitation-heavy)
Use gh api repos/{owner}/{repo}/commits?per_page=10 and gh api repos/{owner}/{repo}/releases?per_page=3 to get recent changes.
2. Evaluate Each New Commit/Release
For each new change since the last update (check the _Last updated date in each file):
- Is it a bug fix? → Check if ARC-1 has the same bug
- Is it a new feature? → Evaluate:
- Does ARC-1 need this feature?
- Should it go in ARC-1 or mcp-sap-docs?
- What's the effort estimate?
- What's the priority?
- Is it a pattern improvement? → Review if ARC-1's implementation can benefit
3. Update Documents
For each project document (docs/compare/01-*.md through docs/compare/07-*.md):
- Update the
## Changelog & Relevance Trackertable with new entries - Update the
_Last updateddate - If a new feature was found, add it to the appropriate "Features This Project Has That ARC-1 Lacks" table
4. Update Feature Matrix
Update docs/compare/00-feature-matrix.md if any project added new capabilities.
5. Update Priority Action Items
Review and re-prioritize the action items at the bottom of 00-feature-matrix.md based on:
- New findings from this scan
- Whether any items have been implemented in ARC-1 since last check
- Changed priority based on ecosystem movement
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.
- 3d ago First seen · 71 lines · 0 tokens per session scan A 735f0f1a3959
compare-projects is a command published in the GitHub repository arc-mcp/arc-1 (174 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 734 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.