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 avivsinai/skills-marketplace --skill amq-specgit clone --depth 1 https://github.com/avivsinai/skills-marketplaceWrote 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/avivsinai/skills-marketplace/amq-spec)<a href="https://agentmods.dev/skills/avivsinai/skills-marketplace/amq-spec"><img src="https://agentmods.dev/badge/skills/avivsinai/skills-marketplace/amq-spec/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/avivsinai/skills-marketplace/amq-spec"><img src="https://agentmods.dev/badge/skills/avivsinai/skills-marketplace/amq-spec.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.00040 | $0.01852 |
| Opus 5 | $0.00020 | $0.00926 |
| Sonnet 5 | $0.00008 | $0.00370 |
| Haiku 4.5 | $0.00004 | $0.00185 |
Grade A, and why
amq-spec 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.
This is a copy
100% identical to amq-spec — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/amq-spec — Collaborative Specification Workflow
This skill defines a structured two-agent specification flow.
Use canonical phases in order:
Research -> Discuss -> Draft -> Review -> Present -> Execute
Detailed step-by-step protocol lives in references/spec-workflow.md.
This file is the concise operational entrypoint.
Parse Input
From the user prompt, extract:
- topic: short kebab-case spec name (e.g.,
auth-token-rotation) - partner: partner agent handle (default:
codex) - problem: the full design problem statement
If topic/problem are unclear, ask for clarification.
Pre-flight
- Verify AMQ is available:
which amq - Verify the AMQ root is discoverable (
.amqrc, AMQ env vars, or the default.agent-maillayout); otherwise run:amq coop init - Use thread name:
spec/<topic>
First Action: Send problem to partner IMMEDIATELY
The entire point of the spec workflow is parallel research — both agents exploring the problem independently, then comparing notes. Every second you spend researching before sending is a second your partner sits idle waiting for the problem statement. That's why the send comes first, even though your instinct might be to "research first to give better context."
amq send --to <partner> --kind question \
--labels workflow:spec,phase:request \
--thread spec/<topic> --subject "Spec: <topic>" --body "<problem>"
Send the user's problem description verbatim — your own analysis goes in the research phase, not the kickoff. If you pre-analyze, you bias the partner's independent research, which defeats the purpose of having two perspectives.
Label Convention
Labels are how both agents and the receiver-side protocol table know which phase the conversation is in. Use existing AMQ kinds plus labels to express spec workflow semantics:
| Phase | Kind | Labels |
|---|---|---|
| Problem statement | question |
workflow:spec,phase:request |
| Research findings | brainstorm |
workflow:spec,phase:research |
| Discussion | brainstorm |
workflow:spec,phase:discuss |
| Plan draft | review_request |
workflow:spec,phase:draft |
| Plan feedback | review_response |
workflow:spec,phase:review |
| Final decision | decision |
workflow:spec,phase:decision |
| Progress/ETA | status |
workflow:spec |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -4 lines · -110 tokens per session dcba282af821
- 7d ago Changed 50c379204054
- 9d ago Changed 28bf56359cd6
- 12d ago First seen · 150 lines · 150 tokens per session scan A f74ed31c6def
amq-spec is a skill published in the GitHub repository avivsinai/skills-marketplace (2 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,852 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to amq-spec, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
a-rules-optimizer
Audit .claude/rules/ and CLAUDE.md against what the codebase actually does.
a-review-optimizer
Read this codebase and write, or sharpen, a review skill fitted to it.
a-review-core
Shared review engine that a project's own review skill reads. Not run on its own.
a-self-learner
Turn recurring review findings into proposed rule and skill updates.
smith
Scaffold a new Quickstop plugin with correct structure and conventions.
sanitize-public
Pre-publish privacy gate. Runs before anything crosses from a private working environment to a public one: a plugin marketplace repo, a downloadable bundle, a public GitHub repo or gist, a shared skill or command. Scans the exact files that will ship for key material, credentials, internal hostnames, LAN IPs, personal…