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 Eliyce/paqad-ai --skill integration-doc-maintainergit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/integration-doc-maintainer)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/integration-doc-maintainer"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/integration-doc-maintainer/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/eliyce/paqad-ai/integration-doc-maintainer"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/integration-doc-maintainer.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.00011 | $0.00596 |
| Opus 5 | $0.00005 | $0.00298 |
| Sonnet 5 | $0.00002 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
integration-doc-maintainer 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 12d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Maintains cross-module integration docs by documenting events, jobs, contracts, and fallback behavior for any change that crosses module or service boundaries.
Use This When
Use this when a request affects published events, consumed events, background jobs, external service contracts, or any cross-module dependency.
Inputs
- Read the current integration docs first:
integration/events.mdandintegration/contracts.mdfor the affected module. - Read the changed code and any generated event inventory or contract references.
- Read
references/integration-contract-fields.mdbefore updating entries.
Procedure
- Run
scripts/find-integration-docs.shto enumerate canonical events/contracts/jobs/integration docs. - Run
scripts/extract-events.sh <changed-files...>to surface candidate event names; LLM confirms each before writing. - Update each event entry using
assets/event.template.md(publisher, subscribers, payload, async behavior, failure expectations, versioning). - Update contracts with owner, versioning, and fallback/degradation behavior. Document both sides of every cross-module coupling.
- Format report per
assets/output.template.mdand validate withscripts/lint-output.sh. Missing fallback / undocumented coupling →## Consistency Warnings, never silent.
Output Contract
- Match
assets/output.template.md:## Updated Integration Docsand## Consistency Warnings. - Every updated item must name the event, contract, job, or integration path and the canonical doc path changed.
- Output must pass
scripts/lint-output.sh(exit 0). - Missing fallback behavior, subscriber ownership, or compatibility policy belongs under
Consistency Warnings, never as an invented completed entry.
Escalate / Stop Conditions
- Ask when subscriber ownership, contract versioning, or fallback policy is unclear.
- Warn when a new integration path has no documented recovery or compatibility posture.
- Do not invent event payloads or subscriber lists that are not evidenced by the code or project docs.
What ships with it
7 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.
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.
- 12d ago First seen · 69 lines · 11 tokens per session scan A c35427d88675
integration-doc-maintainer is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 596 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.