Borrowing it
Nothing to install: this file belongs to hs737/mcp-server-for-ynab. 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/hs737/mcp-server-for-ynab/master/.agents/skills/hardening-review/SKILL.mdgit clone --depth 1 https://github.com/hs737/mcp-server-for-ynabWrote 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/hs737/mcp-server-for-ynab/hardening-review)<a href="https://agentmods.dev/skills/hs737/mcp-server-for-ynab/hardening-review"><img src="https://agentmods.dev/badge/skills/hs737/mcp-server-for-ynab/hardening-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/hs737/mcp-server-for-ynab/hardening-review"><img src="https://agentmods.dev/badge/skills/hs737/mcp-server-for-ynab/hardening-review.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.00025 | $0.00498 |
| Opus 5 | $0.00013 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
hardening-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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardening Review
Use this skill when reviewing a completed feature, workflow, or integration for quality and signoff readiness in this Python repository.
Use When
- Reviewing another agent’s work
- Preparing for merge
- Auditing a feature or phase
- Checking whether implementation is truly complete
- Looking for edge cases and drift
Read First
AGENTS.md(if present)README.mdandpyproject.toml- Relevant architecture docs and tests under
tests/ - Contract or MCP tool schema docs, if present
Core Rules
- “Works on the happy path” is not enough.
- Docs honesty is part of completion.
- Missing or weak tests (
pytest) are a real issue, not a footnote. - Scope, auth, or boundary mistakes are high severity (wrong budget, leaked tokens in logs).
- Generated artifact drift (OpenAPI, schemas) matters when the repo uses codegen.
- Overclaiming implementation is a bug.
- Review should prioritize bugs, regressions, and risks before summaries.
- Run or verify
pytest,ruff,mypy/pyright—whatever this repo’s CI uses—when judging signoff.
Workflow
- Identify the implemented scope.
- Check the actual code path, not just the claimed behavior.
- Review unhappy paths and partial-data behavior (API errors, empty lists, invalid ids).
- Check docs and contract alignment (README, tool descriptions, Pydantic models).
- Check tests for real proof, not only heavy mocking of the code under test.
- Report findings ordered by severity.
- State clearly whether the work is signoff-ready.
Common Failure Modes
- unit tests exist but MCP tools or integrations are untested
- docs still describe old or aspirational behavior
- env vars or secrets handling is unclear or unsafe
- generated artifacts drift from Pydantic/OpenAPI source
- incomplete feature presented as complete
- type hints lie about optional vs required fields
Completion Standard
The work has been checked for implementation reality, unhappy paths, docs honesty, contract alignment, and verification depth, and is clearly judged ready or not ready for signoff.
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.
- 11d ago First seen · 58 lines · 25 tokens per session scan A b4c5a7cc9902
hardening-review is a skill published in the GitHub repository hs737/mcp-server-for-ynab (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 498 once invoked, about $0.0001 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
impl-validator
Validate whether an implementation matches its stated goal. Use this skill when a skill or agent wants a second opinion on its own output, when the user says "check this implementation", "validate what you did", "is this correct?", "review the output", or "did you do this right?". Also spawned automatically as a…
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
invariant-first-testing
Write tests that describe system invariants, not specific bugs. Tests should read like design documentation, not a changelog of failures. Use when writing new tests, reviewing test suites, or refactoring reactive bug-fix tests into invariant-style tests.
refine
Compound quality pass over recently changed code. Orchestrates seven standalone skills in sequence: comment, lerp, style, fix-types, interface, test-invariants, exemplar-audit. Each pass is independently invokable. Use after any feature or refactor lands and before the final commit.
phoenix-review
Review completed work against the Intent Contract's acceptance criteria using objective evidence, not opinion — re-run every check, confirm no regressions, inspect the tamper-evident trace, and surface only real issues (bugs, unmet criteria, regressions). Use before shipping, after a feature is built, or when the user…
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…