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.01077 |
| Opus 5.5 | $0.00016 | $0.00431 |
| Sonnet 5.5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
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 today.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AMQ collaborative specification
Two agents research a design problem independently, discuss it, and converge on one plan. The user approves the plan before anyone implements it.
Phases run in order:
Research -> Discuss -> Draft -> Review -> Present -> Execute
Per-phase commands and the research and plan templates are in the spec workflow.
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>
Kickoff
Send the problem to the partner first, then start your own research. Both agents then research in parallel. Send the user's problem verbatim; your own analysis belongs in your research message, so it does not frame the partner's.
amq send --to "<partner>" --kind question \
--labels workflow:spec,phase:request \
--thread "spec/<topic>" --subject "Spec: <topic>" --body "<problem>"
Labels
Every spec message uses an ordinary AMQ kind plus these labels on the
spec/<topic> thread:
| 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 |
When you receive a spec message
| Label | Your action |
|---|---|
phase:request |
Do your own research first, then send findings as brainstorm + phase:research. |
phase:research |
If you have not sent your own research on this thread, research and send it before you read the partner's. Then read the thread and start discussion as brainstorm + phase:discuss. |
phase:discuss |
Reply with your analysis; continue until aligned. |
phase:draft |
Review the plan and send feedback as review_response + phase:review. Do not implement. |
phase:review |
Revise the plan if needed, or confirm alignment. |
phase:decision |
Stop. Do not implement; see the approval gate below. |
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.
- today Changed a1de8c1b766c
- 2d ago Changed 828ceeb6fad9
- 3d ago Changed fdc3a5d74122
- 4d ago Changed 351dab5bddae
- 8d ago Changed 16feaf57e4db
- 9d ago Changed 03814ce30b0f
- 10d ago Changed c9d477b069e6
- 12d ago Changed · -49 lines 8b534299576a
- 13d ago Changed 8b9afd1c6b52
- 15d ago First seen · 147 lines · 40 tokens per session scan A e8461c0f0377
amq-spec is a skill published in the GitHub repository avivsinai/skills-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,077 once invoked, about $0.0002 per session on Opus 5.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
doc-html-slide
A renderer that turns presentation content into a single HTML slide deck that opens directly in a browser. It creates a 16:9 slide sequence with navigation, fullscreen viewing, printing to PDF, and speaker-note controls.
career-portfolio
A portfolio-building skill for Korean job seekers that organizes projects and explains their work for development, design, marketing, and planning roles.
cs-channel-message
A channel-message writing tool for search ads, advertising, customer relationship messages, and app notifications. It uses the NCM sequence—Need, Channel, Moment, Message, and CTA—to adapt wording to where and when customers see it.
media-gemini-3-image-prompt
A prompt builder for Gemini 3 Pro Image, also known as Nano Banana Pro, Google's image-generation model. It expands a short request into five parts covering the subject, action, setting, composition, lighting, style, and text constraints.
doc-pptx
A PowerPoint (.pptx) presentation generator and designer for business reports, investor pitches, training materials, conference talks, and product demos. It can build slides from direct content, HTML, NotebookLM, or a Markdown script.
setup-mcp-connector
A step-by-step setup guide for connecting Cowork to services such as Google Drive, Notion, and Higgsfield, plus Korean public-data, document, statistics, architecture, and law services. It explains authentication, API keys, test calls, and troubleshooting.