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 agentmods add skills/qte77/claude-code-plugins/enforcing-doc-hierarchynpx skills add qte77/claude-code-plugins --skill enforcing-doc-hierarchygit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/enforcing-doc-hierarchy)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/enforcing-doc-hierarchy"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/enforcing-doc-hierarchy.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 | $0.00037 | $0.01497 |
| Opus 5 | $0.00018 | $0.00749 |
| Sonnet 5 | $0.00007 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
enforcing-doc-hierarchy 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enforce Documentation Hierarchy
Scope: $ARGUMENTS
Audits documentation against the project's declared hierarchy, then aligns violations with user approval.
Phase 1: Discover
The authoritative hierarchy lives where the
qte77 doc-structure canon
(SoT) places it: CONTRIBUTING.md's ## Documentation hierarchy statement. The canon's model is
README = the project contract, CONTRIBUTING = conventions + the hierarchy statement,
AGENTS = behavioural rules, CLAUDE = a one-line @AGENTS.md pointer (never a copy).
Read the project's declaration, looking in order:
CONTRIBUTING.md—## Documentation hierarchysection (canonical location; table or list)AGENTS.md— "Key references" or "Information sources" sectionREADME.md— "Documentation" / "Refs" section (links to authoritative docs)
Extract:
- Entry points: which docs are human vs agent entry points
- Authority map: which doc owns which content type
- Anti-redundancy rule: stated or implied (default: no duplication across docs)
If no hierarchy is declared, report that as the first finding and stop. Treat the canon model above as the expected baseline and flag deviations from it.
Phase 2: Audit
Detect violations across the scope. For each finding, record:
| Source File | Line | Type | Description |
|---|---|---|---|
| path | Lnn | type | what's wrong |
Violation Types
- broken-link: Reference target does not exist (moved, renamed, deleted, wrong case)
- duplicate: Same content (3+ lines) appears in both an authority doc and a dependent doc
- misplaced: Content is in the wrong doc per the discovered authority map, OR a doc in the hierarchy is not referenced by its parent
- lint-compat: HTML comments before frontmatter
- config-drift: Inline
<!-- markdownlint-disable/enable -->for a rule already disabled in.markdownlint.json. These are dead code that causes false positives when the enable directive re-activates a globally-disabled rule - unused-link-def:
[key]: urllink definition with no corresponding[text][key]or[key]reference in the file
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 First seen · 136 lines · 37 tokens per session scan A bfa41a90ff95
enforcing-doc-hierarchy is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,497 once invoked, about $0.0002 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
orchestrator
FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.
flutter-guide
Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.
maestro-flutter
Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
codex-advisor
Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…