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 skyf0xx/hedgehog --skill hedgehog-dailygit clone --depth 1 https://github.com/skyf0xx/hedgehogWrote 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/skyf0xx/hedgehog/hedgehog-daily)<a href="https://agentmods.dev/skills/skyf0xx/hedgehog/hedgehog-daily"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/hedgehog-daily/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/skyf0xx/hedgehog/hedgehog-daily"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/hedgehog-daily.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.00000 | $0.01409 |
| Opus 5 | $0.00000 | $0.00705 |
| Sonnet 5 | $0.00000 | $0.00282 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
hedgehog-daily 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 8d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily change-work
One gate, three exits, for every change request on a project whose build
graph already exists. It reads the installed core's layer sequence,
scope globs and verify commands out of .hedgehog/core.yaml, so it is
the same gate on every core.
The gate exists to stop pricing a two-line edit at the cost of the largest change the discipline can handle. Routing up is a real decision with a real cost, taken on stated conditions — not the safe default.
Entry
.hedgehog/exists. Without it there is no core to read and no graph to add to; this skill does not apply.- Nothing is in flight.
hedgehog status --brief— one line. If it names any task, a build is mid-flight: this gate does not run. Read the fullhedgehog statusand hand the request back to the core's own loop skill, which owns work in progress. - Read
.hedgehog/core.yaml. The layer list is the input to every decision below: each layer'sid,scopeglobs,verifycommand,verify_radiusandexclusive. Read the file, not a memory of it.
The three exits
Decide by the conditions, in order. The first one that holds is the exit. Re-plan is checked first, and its check is a read to make, not a suspicion to already hold — do not reach Change-work or Tweak without having made it.
Re-plan
The core's own loop skill names which artifact governs this project —
the brief and layer sequence for a shipped core, .hedgehog/core-design.md
for an authored one, .hedgehog/adoption.md for an adopted one. Read
that artifact, then check:
- Does anything the request needs contradict a statement locked there — an interface, a stack choice, a scope boundary?
If it holds, this is Re-plan — regardless of how many layers the request
reaches or whether every file it touches already exists. Route to
planner's re-entry pass, which adds intents for new work without
re-running planning from scratch and without disturbing anything already
built.
Where the contradiction means the request is a different project rather than an extension of this one, say so plainly instead of routing. That artifact is never rewritten to accommodate new scope.
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.
- 8d ago Changed · +9 lines 37b3a1f33674
- 12d ago First seen · 126 lines · 0 tokens per session scan A 3a27580816b2
hedgehog-daily is a skill published in the GitHub repository skyf0xx/hedgehog (38 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,409 tokens. 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
writing-skills
Use when creating a new skill for the Shipworthy plugin, or when a recurring failure mode needs to be codified into a reusable guide. Covers TDD-for-documentation, CSO (Claude Search Optimization), adversarial testing, and the full skill lifecycle.
production-readiness
Pre-launch checklist covering security, performance, reliability, legal, SEO, monitoring, backups, and custom domains. Each item has both a plain-language explanation and technical implementation detail. Ensures nothing critical is missed before going live.
compliance-awareness
Practical engineering guidance for SOC 2, GDPR, HIPAA compliance and data classification. Covers access controls, audit logging, change management, right to deletion, data portability, consent, PHI encryption, and data classification levels. Engineering checks, not legal advice.
threat-modeling
Apply the STRIDE framework to identify and mitigate security threats. Covers Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege with practical questions, verification steps, and mitigations for each threat category.
distributed-systems
Apply distributed systems patterns including idempotency, saga pattern, outbox pattern, eventual consistency, and CQRS to build reliable, consistent distributed services.
twelve-factor-app
Evaluate and apply the Twelve-Factor App methodology with modern 2025 interpretations. Covers all 12 factors with actionable checks for cloud-native applications running on containers, Kubernetes, and serverless platforms.