Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/pactflow/pactflow-agent-skillsnpx agentmods add skills/pactflow/pactflow-agent-skills/asyncapi-parserWrote 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-parser)<a href="https://agentmods.dev/skills/pactflow/pactflow-agent-skills/asyncapi-parser"><img src="https://agentmods.dev/badge/skills/pactflow/pactflow-agent-skills/asyncapi-parser/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-parser"><img src="https://agentmods.dev/badge/skills/pactflow/pactflow-agent-skills/asyncapi-parser.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.00160 | $0.02124 |
| Opus 5.5 | $0.00064 | $0.00850 |
| Sonnet 5.5 | $0.00032 | $0.00425 |
| Haiku 4.5 | $0.00016 | $0.00212 |
Grade A, and why
asyncapi-parser 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AsyncAPI Parser Skill
AsyncAPI version: This skill targets AsyncAPI 3.x (3.0 and 3.1). AsyncAPI 2.x is NOT supported by Drift — if the spec has
asyncapi: "2.x.x", tell the user and stop.
Reference files
references/asyncapi-schema-patterns.md— how to read and enumerate AsyncAPI 3.x message schemas (oneOf / anyOf / allOf / discriminator / const / correlationId / optional payload fields)references/asyncapi-drift-mapping.md— how to map each execution mode and payload variant to Drift YAML, including trigger/probe patterns,expectedstructure per mode, and naming conventions
Workflow
0. Navigate large specifications without loading them wholesale
For a specification over 1,000 lines or 100 KB, do not read or paste the whole file. Build a line-number index, then inspect only the operation and definitions that are reachable from it:
# Establish the document size and top-level section boundaries.
wc -l -c asyncapi.yaml
grep -nE '^(operations|channels|components):' asyncapi.yaml
# List AsyncAPI operation IDs without reading their bodies.
awk '/^operations:/{in_operations=1; next} in_operations && /^[^ ]/{exit} in_operations && /^ [A-Za-z0-9._-]+:$/ {print NR ":" $0}' asyncapi.yaml
For a requested operation, locate its line number, then use sed -n to read a
bounded range ending at the next operation at the same indentation. Follow the
same pattern for the referenced channel, message, and schema definitions. Never
expand unrelated operations, channels, or every item under components merely
to find a match.
Keep a compact fact ledger while resolving references:
| item | source line | refs still to resolve | resolved facts |
|---|---|---|---|
| operation | action, channel, messages, reply | ||
| channel | address | ||
| message | correlation ID, headers, payload ref | ||
| schema | variants, required fields, discriminator |
What ships with it
11 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/01-send-observe-basic.json 1.2 KB
- evals/02-receive-inject-payload-variants.json 1.3 KB
- evals/03-request-reply-operation.json 1.2 KB
- evals/04-very-long-spec-navigation.json 1.2 KB
- evals/05-complex-schema-variants.json 998 B
- evals/fixtures/inventory.asyncapi.yaml 1.9 KB
- evals/fixtures/order.asyncapi.yaml 1.2 KB
- evals/fixtures/platform.asyncapi.yaml 3.1 KB
- evals/fixtures/pricing.asyncapi.yaml 2.4 KB
- references/asyncapi-drift-mapping.md 9.5 KB
- references/asyncapi-schema-patterns.md 5.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 · 193 lines · 160 tokens per session scan A a4fa319a5f12
asyncapi-parser is a skill published in the GitHub repository pactflow/pactflow-agent-skills (7 stars, last pushed yesterday), licensed MIT. It adds 160 tokens to every session and 2,124 once invoked, about $0.0006 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
xdto-validate
A validator for XDTO packages in 1C:Enterprise. It checks the package model, its metadata object, and its connection to the configuration.
API Contract Validator
Validate API responses against OpenAPI/Swagger specifications, JSON Schema definitions, and consumer-driven contracts to prevent breaking changes.
Contract Test Generator
Generate consumer-driven contract tests using Pact framework to verify API provider-consumer compatibility and prevent integration breaking changes.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.
feature-verify
Feature verification (READ-ONLY, P0-P5). Use when: verifying feature behavior after deployment, validating API responses, diagnosing production issues, post-deploy smoke test. Not for: modifying data (use feature-dev), code review (use codex-review-fast), writing tests (use codex-test-gen), security audit (use…
post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.