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/bryntay/a1-mcpWrote 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/bryntay/a1-mcp/reference)<a href="https://agentmods.dev/commands/bryntay/a1-mcp/reference"><img src="https://agentmods.dev/badge/commands/bryntay/a1-mcp/reference/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/commands/bryntay/a1-mcp/reference"><img src="https://agentmods.dev/badge/commands/bryntay/a1-mcp/reference.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.00010 | $0.00169 |
| Opus 5.5 | $0.00004 | $0.00068 |
| Sonnet 5.5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
reference 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.
What it actually says
Find reference in A1 Gallery for: $ARGUMENTS
Run the search, then report back:
- Rephrase the brief in the gallery's taxonomy terms and call
search_websites. If the brief names a section rather than a whole site — a hero, a pricing table — usesearch_sectionsinstead. - Return five or six matches. For each, give the site name, its live URL, and the one thing that makes it a match for this brief. Not a list of its tags.
- If the response carries
broadenedSearch, say which terms were dropped and that the matches are looser than asked for.
Skip the preamble. Lead with the matches.
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 · 19 lines · 10 tokens per session scan A caa4ca6ef446
reference is a command published in the GitHub repository bryntay/a1-mcp (1 stars, last pushed 8d ago), licensed MIT. It adds 10 tokens to every session and 169 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
port_to_platform
Take an existing design or implementation to another platform (iOS ↔ Android ↔ macOS ↔ web) — porting the intent and IA, not the components.
compile
Compile a FIBER decision context (world + query) and report the oracle verdict, omission accounting, and certificate digest faithfully.
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.