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 pactflow/pactflow-agent-skills --skill asyncapi-generatorgit clone --depth 1 https://github.com/pactflow/pactflow-agent-skillsWrote 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/pactflow/pactflow-agent-skills/asyncapi-generator)<a href="https://agentmods.dev/skills/pactflow/pactflow-agent-skills/asyncapi-generator"><img src="https://agentmods.dev/badge/skills/pactflow/pactflow-agent-skills/asyncapi-generator/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/pactflow/pactflow-agent-skills/asyncapi-generator"><img src="https://agentmods.dev/badge/skills/pactflow/pactflow-agent-skills/asyncapi-generator.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.00205 | $0.02948 |
| Opus 5.5 | $0.00082 | $0.01179 |
| Sonnet 5.5 | $0.00041 | $0.00590 |
| Haiku 4.5 | $0.00020 | $0.00295 |
Grade A, and why
asyncapi-generator 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 15d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AsyncAPI Generator
Generates an AsyncAPI 3.x spec by statically analysing a service codebase with ripwire.
The spec may be incomplete (stub payloads where the shape can't be resolved), but it is always
valid AsyncAPI 3.x and immediately usable as input to asyncapi-parser and Drift.
This is the async counterpart of oas-generator. The key difference: HTTP routes are declared in
one place, but messaging topology is scattered — a topic name appears in a producer call, a
consumer decorator, a config file and an env var. Most of the work is finding every send/receive
site and resolving the channel name behind it.
Prerequisites: ripwire on PATH. If absent, see pact-coverage/references/install-ripwire.md.
AsyncAPI 2.x is not supported by Drift, so always emit asyncapi: "3.0.0".
Read references/broker-patterns.md for grep patterns per
broker/library. Read it in Step 2; don't load it earlier.
Step 1 — Identify broker and language
ripwire <service-root> --for="message producers and consumers publishing and subscribing to topics queues"
Confirm with dependency manifests (package.json, pom.xml/build.gradle, requirements.txt/
pyproject.toml, go.mod, Gemfile): kafkajs, spring-kafka, confluent-kafka, aws-sdk
SNS/SQS clients, boto3, amqplib/pika, nats, google-cloud-pubsub, mqtt, ws.
A service often uses more than one broker; record all of them. If nothing messaging-related is found, tell the user — don't invent channels.
Step 2 — Find every send and receive site
Use the patterns in references/broker-patterns.md for the detected broker(s), passed to
ripwire <root> --regex='<pattern>'. Use --regex, not --grep: --grep is a literal match, so a
pattern with | alternation returns zero hits, and ripwire reports that zero as complete. If a
search returns files="0", the root path is wrong or unindexed, not proof that nothing publishes.
Run each applicable pattern and deduplicate. For every hit, note the enclosing symbol (in=) and
classify it:
What ships with it
18 files 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.
- evals/evals.json 4.5 KB
- evals/fixtures/kafka-orders/package.json 70 B
- evals/fixtures/kafka-orders/src/consumer.js 583 B runs code
- evals/fixtures/kafka-orders/src/publisher.js 428 B runs code
- evals/fixtures/kafka-orders/src/topics.js 94 B runs code
- evals/fixtures/kafka-orders/test_publisher.test.js 101 B runs code
- evals/fixtures/spring-billing/build.gradle 77 B
- evals/fixtures/spring-billing/src/main/java/com/acme/billing/Events.java 373 B
- evals/fixtures/spring-billing/src/main/java/com/acme/billing/Invoice.java 290 B
- evals/fixtures/spring-billing/src/main/java/com/acme/billing/InvoiceEventPublisher.java 951 B
- evals/fixtures/spring-billing/src/main/java/com/acme/billing/InvoiceService.java 525 B
- evals/fixtures/spring-billing/src/main/java/com/acme/billing/PaymentListener.java 894 B
- evals/fixtures/spring-billing/src/main/java/com/acme/billing/TopicProperties.java 513 B
- evals/fixtures/spring-billing/src/main/resources/application.yml 228 B
- evals/fixtures/spring-billing/src/test/java/com/acme/billing/PublisherTest.java 128 B
- evals/fixtures/sqs-notifier/notifier.py 764 B runs code
- evals/fixtures/sqs-notifier/requirements.txt 16 B
- references/broker-patterns.md 4.7 KB
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.
- 15d ago First seen · 247 lines · 205 tokens per session scan A 0ee1f9b36107
asyncapi-generator is a skill published in the GitHub repository pactflow/pactflow-agent-skills (7 stars, last pushed yesterday), licensed MIT. It adds 205 tokens to every session and 2,948 once invoked, about $0.0008 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-10-02.
Other skills, from other repositories
demographic-modeling
This skill should be used when the user asks to "design a demographic model", "model a person/organisation/role", "design party relationships", "plan identity structures", or "work with demographic archetypes". Covers designing openEHR demographic models using the PARTY hierarchy, roles, capabilities, relationships…
epf-bsp-init
A helper for describing a 1C external report or data processor so it can be added through the platform’s standard “Additional reports and processors” section.
platform-help
A reference skill for the 1C platform and BSL, the programming language used to build 1C business applications. It helps clarify the platform’s object model, APIs, versions, and compatibility.
epf-init
A starter structure for a 1C external data processor, packaged as source files that the 1C Designer can use to build the processor file.
interface-edit
Guidance for configuring a 1C subsystem’s command interface, the area where users find and run commands.
meta-add
A tool for creating one typed 1C metadata object, with optional immediate configuration. 1C metadata objects define parts of an application, such as documents or directories.