Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vladm3105/aidoc-flow-framework/plugin install aidoc-flowWrote 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/vladm3105/aidoc-flow-framework/doc-chg-audit)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-chg-audit"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-chg-audit/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/vladm3105/aidoc-flow-framework/doc-chg-audit"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-chg-audit.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.00069 | $0.09039 |
| Opus 5 | $0.00034 | $0.04519 |
| Sonnet 5 | $0.00014 | $0.01808 |
| Haiku 4.5 | $0.00007 | $0.00904 |
Grade A, and why
doc-chg-audit 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 4d 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 — 703 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-chg-audit
Purpose
Run a unified CHG audit — declarative schema checks plus impact, cascade,
gate-routing, change-level, and content-quality review — in one pass, producing
a single combined report that ../doc-chg-fixer/SKILL.md consumes. The
framework ships no runtime code, so this skill is the validator: Claude
performs each check directly against the CHG record using the spec as the
contract. In team mode, this skill fans out the CHG crew
(integration_lead/architect/chaos_engineer/operator/auditor/security_engineer)
per ${CLAUDE_PLUGIN_ROOT}/framework/governance/REVIEW_TEAM.md §Operations
§Review.
CHG is NOT a lifecycle layer in the BRD..IPLAN sense: it has no readiness
score. This audit therefore reports gate-readiness as a pass/fail plus a
fix list — it does not compute a 0–100 readiness score. The quality bar is
gate approval, granted by a human via ../gate-check/SKILL.md, not by a
number. For team-mode dispatch purposes the CHG layer is addressed as
09_CHG (the layer-id slot occupied by the change-management overlay).
Scope: a CHG can touch any artifact along
BRD → PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN → Code.
Upstream: a CHG record. Downstream:
.aidoc/audit/09_CHG-audit.md and an optional fix-cycle trigger.
When to Use
Use after a CHG record exists and before handing it to ../gate-check/SKILL.md
for C3/Emergency approval, or inside the autopilot's audit↔fix cycle. Do not
use to author a CHG (use ../doc-chg/SKILL.md or ../doc-chg-autopilot/SKILL.md)
or to run the formal gate itself (that is ../gate-check/SKILL.md).
Fresh-audit policy: always audit from scratch — never reuse prior results; re-evaluate gate-readiness independently each run.
Report cleanup: the audit report is a single file
(.aidoc/audit/09_CHG-audit.md) overwritten in place each run — no version
cleanup needed. Keep CHG-NN.F_fix_report_v*.md.
Execution Contract
Input: CHG path (docs/governance/chg/CHG-NN_*..., or
CHG-EMG-YYYYMMDD-HHMM for Emergency).
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.
- 4d ago Changed 932bf6440384
- 5d ago Changed b29e885a2538
- 9d ago First seen · 703 lines · 69 tokens per session scan A e7339279299c
doc-chg-audit is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 9,039 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.