Borrowing it
Nothing to install: this file belongs to netdevops/hier_config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/netdevops/hier_config/master/.claude/skills/hier-config-review/SKILL.mdgit clone --depth 1 https://github.com/netdevops/hier_configWrote 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/netdevops/hier_config/hier-config-review)<a href="https://agentmods.dev/skills/netdevops/hier_config/hier-config-review"><img src="https://agentmods.dev/badge/skills/netdevops/hier_config/hier-config-review/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/netdevops/hier_config/hier-config-review"><img src="https://agentmods.dev/badge/skills/netdevops/hier_config/hier-config-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00884 |
| Opus 5.5 | $0.00018 | $0.00354 |
| Sonnet 5.5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
hier-config-review 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 1mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hier_config Change Review
Review the current change set against this repository's standards and report findings. Do not fix anything unless explicitly asked — the deliverable is the review report.
Step 1: Establish the Diff
git diff master...HEAD --stat # on a branch
git diff HEAD --stat # fall back: uncommitted work
git diff --staged --stat # fall back: staged only
List every changed file and classify it: library code (hier_config/), tests (tests/), docs (docs/, mkdocs.yml), CI/config, or CHANGELOG.md. Read the full diff for each classified file before judging it.
Step 2: Run the Gates
Run these and report exact failures (tool, file, line, message):
poetry run ./scripts/build.py lint
poetry run ./scripts/build.py pytest --coverage
If docs/ or mkdocs.yml changed, also run:
poetry run mkdocs build --strict
Step 3: Review by Category
Read the referenced doc before judging that category — the docs are the standard, not your intuition.
Models & Typing — read docs/dev/code-style.md
- New Pydantic models subclass the local
BaseModel(hier_config/models.py), neverpydantic.BaseModeldirectly. - Model fields use
tuple/frozenset, neverlist/set. Rule models usematch_rules: tuple[MatchRule, ...]. - No
Any, no missing annotations, no unjustified# type: ignore/# noqa. - Lint/coverage/type-checking configuration was not loosened.
Tests & TDD — read docs/dev/testing.md
- Every library code change has corresponding tests.
- Tests are flat functions with full annotations; no test classes (benchmarks excepted).
- Driver changes are tested in
tests/test_driver_<platform>.py; view changes intests/config_view/. - Driver/rule behavior changes include the round-trip idiom: remediation asserted via
dump_simple()tuple, rollback verified via nounified_diff. - New fixtures live in
tests/fixtures/with module-scoped accessors intests/conftest.py.
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.
- 1mo ago First seen · 81 lines · 46 tokens per session scan A 0e9002c7889a
hier-config-review is a skill published in the GitHub repository netdevops/hier_config (152 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 884 once invoked, about $0.0002 per session on Opus 5.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-09-01.
Other skills, from other repositories
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…
full-stack-e2e-review
Run a rigorous end-to-end product or feature review across architecture, data, APIs, permissions, billing, tests, and real browser UX. Use for requests such as review this branch end to end, test everything, ensure no bugs, perform a full visual pass, or validate a multi-user workflow before merge or deploy.