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-iplan-audit)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-iplan-audit"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-iplan-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-iplan-audit"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-iplan-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.00043 | $0.08007 |
| Opus 5 | $0.00022 | $0.04004 |
| Sonnet 5 | $0.00009 | $0.01601 |
| Haiku 4.5 | $0.00004 | $0.00801 |
Grade A, and why
doc-iplan-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 3d 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.
This is a copy
75% identical to doc-bdd-audit — 312 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 652 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-iplan-audit
Purpose
Run a unified IPLAN audit — declarative structural checks plus
content-quality review — in one pass, producing a single combined report that
../doc-iplan-fixer/SKILL.md consumes. The framework ships no runtime code, so
this skill is the validator: Claude performs each check directly against the
IPLAN using the spec as the contract.
Layer: 8 (IPLAN quality gate). Upstream: an IPLAN file. Downstream:
.aidoc/audit/08_IPLAN-audit.md and an optional fix-cycle trigger.
When to Use
Use after an IPLAN exists and before code implementation begins, or inside the
autopilot's audit↔fix cycle. Do not use to create an IPLAN (use
../doc-iplan/SKILL.md or ../doc-iplan-autopilot/SKILL.md).
Fresh-audit policy: always audit from scratch — never reuse prior scores or cached results; compute the CODE-Ready score independently each run.
Report cleanup: the audit report is a single file
(.aidoc/audit/08_IPLAN-audit.md) overwritten in place each run — no version cleanup
needed. Keep IPLAN-NN.F_fix_report_v*.md and .drift_cache.json.
Execution Contract
Input: IPLAN path (docs/08_IPLAN/IPLAN-NN_*.yaml); optional score
threshold (default 90).
Sequence: 1) run structural checks → 2) record findings → 3) run content
review (per §Review Mode below — team fans out lens subagents with per-lens
playbook briefs, single_pass runs every lens sequentially in this skill's
own context) → 3a) load each lens's layer-and-lens playbook from
framework/playbooks/08_IPLAN/<lens>.md and inline it under the lens's brief
(team mode) or apply its checks sequentially (single_pass) → 4) merge/normalize
findings, including a playbook-coverage line surfacing which lenses ran with
their playbook attached → 5) write .aidoc/audit/08_IPLAN-audit.md → 6) if
auto-fixable findings exist, hand off to doc-iplan-fixer.
Review Mode
Resolve review_mode from .aidoc/profile.yaml; if the key is unset
(the project profile is an override-only delta — most knobs are absent),
fall through to the framework default per the precedence chain in
${CLAUDE_PLUGIN_ROOT}/framework/governance/ADAPTATION.md (framework defaults < user-global seed < project profile). The framework default
is team at gates (pre_promotion / pre_merge) and single_pass at
write-time (on_author). The same fallback rule applies to every other
adaptation knob (audit_threshold, section_toggles, active_layers,
glossary). The structural checks below are run deterministically by
this skill in every mode — they are the gate floor per
${CLAUDE_PLUGIN_ROOT}/framework/governance/REVIEW_TEAM.md §"Scoring,
conflicts & the gate".
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.
- 3d ago Changed 029e27f37ad9
- 4d ago Changed · +1 lines d143797f1de7
- 8d ago First seen · 651 lines · 43 tokens per session scan A cbeb4f24433b
doc-iplan-audit is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 8,007 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to doc-bdd-audit, differing in 312 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…