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-ears-autopilot)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-ears-autopilot"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-ears-autopilot/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-ears-autopilot"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-ears-autopilot.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.00056 | $0.02224 |
| Opus 5 | $0.00028 | $0.01112 |
| Sonnet 5 | $0.00011 | $0.00445 |
| Haiku 4.5 | $0.00006 | $0.00222 |
Grade A, and why
doc-ears-autopilot 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-ears-autopilot
Purpose
Automated EARS generation pipeline. From an upstream PRD, a user prompt, or
an implementation plan (IPLAN-*), it analyzes the source, verifies upstream
readiness, generates a complete EARS document of atomic WHEN-THE-SHALL-WITHIN
statements, validates readiness, maintains EARS-00_index.md, and drives the
audit↔fix cycle to a passing score — for one EARS or a batch.
Layer: 3. Upstream: a PRD (and its BRD), a prompt, or an IPLAN. Downstream: a validated EARS + index entry.
Skill Dependencies
| Skill | Role |
|---|---|
../doc-ears/SKILL.md |
EARS structure, the four patterns, syntax rules |
../doc-ears-audit/SKILL.md |
quality gate (scoring + findings) |
../doc-ears-fixer/SKILL.md |
applies fixes from the audit report |
../doc-naming/SKILL.md |
element-ID standards and @threshold: tags |
Input Contract
Accepts: a target EARS id/path; an upstream PRD id/path; a free-text prompt; or an IPLAN path. Optional: score threshold (default 90), max fix iterations (default 3), batch list. With no explicit input, treat the request as a prompt.
Smart Document Detection
For each target, check whether the EARS already exists (nested folder
docs/03_EARS/EARS-NN_{slug}/):
- Missing → generate mode (from the upstream PRD / prompt / IPLAN).
- Exists → review & fix mode (audit, then fix if below threshold).
Determine deliverable_type (code/document/ux/risk/process,
inherited from the upstream PRD) from the source content.
Model precheck
Advisory, best-effort. Surfaces the model you recommended for this layer; it cannot switch the session model. Before invoking the driver:
- If
.claude/aidoc-flow.config.yamlis absent, or has nomodel.*keys, skip this section entirely (no output). - Resolve the recommended model:
model.per_layer.EARSif set, elsemodel.default. - Act on
model.precheck(warn|silent|block):warn(default) — print one line, then continue to the driver:ℹ EARS recommends model '<rec>'. If you're not on it, run /model <rec> (or set model.precheck: silent to hide this).silent— print nothing; continue.block— print the line above plusprecheck=block: confirm you want to draft on the current model, or run /model <rec> first., then wait for the user to confirm before continuing.
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 cb529d09e86e
- 5d ago Changed bcfe93b38f14
- 9d ago First seen · 185 lines · 56 tokens per session scan A 70bdc7b9bc0b
doc-ears-autopilot is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 2,224 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
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…