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 skills add asimons81/hermes-field-kit --skill repo-readiness-auditgit clone --depth 1 https://github.com/asimons81/hermes-field-kitWrote 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/asimons81/hermes-field-kit/repo-readiness-audit)<a href="https://agentmods.dev/skills/asimons81/hermes-field-kit/repo-readiness-audit"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-field-kit/repo-readiness-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/asimons81/hermes-field-kit/repo-readiness-audit"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-field-kit/repo-readiness-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 114 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00048 | $0.03880 |
| Opus 5 | $0.00024 | $0.01940 |
| Sonnet 5 | $0.00010 | $0.00776 |
| Haiku 4.5 | $0.00005 | $0.00388 |
Grade A, and why
repo-readiness-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 12d 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 — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Readiness Audit
Overview
Use this skill to answer a broad repository-state question before new work begins. It determines whether the repository is ready for further development, release work, a new feature, a handoff, or a new contributor.
This is a read-only evidence audit. It does not repair findings. It does not equate a clean working tree, passing tests, or a green local build with overall repository readiness. It verifies each relevant surface independently and records any surface that could not be checked.
This skill covers repository-level readiness. Packaging integrity, upgrade rehearsal, registry publication, signed artifacts, deployment verification, and post-release checks require additional release-specific evidence. When those surfaces matter but cannot be inspected, record them under Not Verified and reduce the verdict accordingly.
When to Use
Load this skill for requests such as:
- "Is this repo ready for further development?"
- "Where did we leave off?"
- "Can I start the next feature?"
- "Audit this repository before we continue."
- "Is everything merged, tested, and documented?"
- "Give me a release-readiness check."
- "What is blocking this project?"
- "Is this ready to hand to another developer?"
- "Can a new contributor safely start here?"
A repository must be identified by an exact local path, a repository URL, or a current working directory that can be verified as a Git repository.
Counter-Triggers
Do not load this skill for:
- A simple code review of one file or one diff.
- Implementing a feature, bug fix, migration, or refactor.
- Automatically fixing every issue found.
- Generic Git or GitHub explanations.
- A feature-duplication investigation focused only on whether one proposed feature already exists.
- An incoming prototype assessment focused only on real versus simulated code.
- A packaging-only, artifact-signing, publication, or post-release verification audit.
- Any request where no repository has been identified.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/clean-ready.md 1.5 KB
- examples/incomplete-access.md 1.6 KB
- examples/not-ready-failing-ci.md 1.4 KB
- README.md 4.6 KB
- references/audit-protocol.md 5.0 KB
- references/evidence-and-access.md 2.4 KB
- references/report-contract.md 1.8 KB
- references/untrusted-content.md 623 B
- references/verdict-rules.md 3.3 KB
- scripts/validate_bundle.py 11 KB runs code
- tests/cases.json 2.8 KB
- tests/contract-cases.json 5.4 KB
- tests/test_contracts.py 8.2 KB runs code
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.
- 12d ago First seen · 511 lines · 48 tokens per session scan A e94e9f666168
repo-readiness-audit is a skill published in the GitHub repository asimons81/hermes-field-kit (125 stars, last pushed 2d ago), licensed Apache-2.0. It adds 48 tokens to every session and 3,880 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-30.
Other skills, from other repositories
orchestrate
Coordinate an active Hardproof run across discovery, design, planning, implementation, review, verification, delivery, and learning.
review
Challenge a Hardproof implementation during REVIEW against its approved contract, code quality, tests, and risk boundaries.
pir-action-tracker
Parses Post-Incident Review (PIR) pages in a Confluence space, fetches live status from referenced Jira tickets, updates action item tables with current status and due dates, marks completed PIRs with a visual closure panel, and surfaces any overdue actions for follow-up. Designed for Customer Success, Support, and…
style-guide
Dedalus style guide quick reference. Key rules for writing code that lasts. Use when writing or reviewing Python code.
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
deliver
Prepare an inspectable Hardproof delivery during DELIVER with final scope, evidence, risks, rollback, and reproducible reporting.