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)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-chg"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-chg.svg" alt="Measured on agentmods" 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.00082 | $0.02683 |
| Opus 5 | $0.00041 | $0.01341 |
| Sonnet 5 | $0.00016 | $0.00537 |
| Haiku 4.5 | $0.00008 | $0.00268 |
Grade A, and why
doc-chg 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 2d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-chg
Purpose
Author a Change Management (CHG) record — the governance overlay for modifying existing SDD artifacts. CHG is NOT a lifecycle layer: no layer number, no readiness score. Triggered on-demand when an artifact must change; quality bar is gate approval, not a numeric score.
Cross-layer scope: a CHG can touch any artifact along
BRD → PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN → Code. Job: classify,
route to the correct gate, trace the cascade, keep the registry honest.
When to Use
Use doc-chg when:
- An existing artifact (any layer) needs a correction, refinement, or cross-layer change.
- A production incident forces an emergency fix that must be documented.
- An external trigger (regulatory, vendor, market) requires a controlled change.
Do not use it to author a brand-new artifact — use the relevant layer skill
(../doc-brd/SKILL.md … ../doc-iplan/SKILL.md). For end-to-end CHG drafting
with minimal prompts, use ../doc-chg-autopilot/SKILL.md.
Prerequisites
Before writing, read:
- Template (source of truth):
${CLAUDE_PLUGIN_ROOT}/framework/governance/chg/CHG-TEMPLATE.yaml - CHG overview:
${CLAUDE_PLUGIN_ROOT}/framework/governance/chg/README.md - Index template:
${CLAUDE_PLUGIN_ROOT}/framework/governance/chg/CHG-00_index.TEMPLATE.md - Authoring style:
${CLAUDE_PLUGIN_ROOT}/framework/governance/AUTHORING_STYLE.md - The entry gate for the change source (see routing below), under
${CLAUDE_PLUGIN_ROOT}/framework/governance/chg/gates/.
Confirm no ID collision: ls docs/governance/chg/ 2>/dev/null. Reserve the next
free CHG-NN (dash form — CHG carries no hierarchical 4-segment element IDs).
Change-Level Classification (decide first)
Classification drives the entire process. Authority:
${CLAUDE_PLUGIN_ROOT}/framework/governance/chg/CHG-TEMPLATE.yaml (metadata.change_level).
| Level | Scope | Gate | Process |
|---|---|---|---|
| C1 | Typo, formatting, clarification | None | Fix → commit → done |
| C2 | Section update, requirement refinement | Peer review | Assess impact → update → verify |
| C3 | Cross-layer change, new requirements | Formal gate | Full CHG process + GATE_APPROVAL_FORM |
| Emergency | Critical production issue (P0/P1) | Post-hoc gate + post-mortem | Fix → deploy → document → post-mortem within 48h |
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.
- 2d ago Changed 1a2bf1ae15d0
- 3d ago Changed e705bd6d3325
- 7d ago First seen · 198 lines · 82 tokens per session scan A ffa0d73646e5
doc-chg is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 2,683 once invoked, about $0.0004 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.