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 no-history-in-outputgit 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/no-history-in-output)<a href="https://agentmods.dev/skills/skyf0xx/hedgehog/no-history-in-output"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/no-history-in-output/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/no-history-in-output"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/no-history-in-output.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.00085 | $0.00448 |
| Opus 5 | $0.00043 | $0.00224 |
| Sonnet 5 | $0.00017 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
Grade A, and why
no-history-in-output 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.
What it actually says
No History in Output
Project-facing documents describe the current state of the thing, not the process that produced it.
Rules
- Never include labels like "(unchanged)", "(updated)", "(new)", "(revised)", or similar edit-tracking annotations in headings or body text.
- Never narrate the discussion that led to a decision (e.g. "we considered X but decided against it," "originally this was Y, now it's Z," "per your feedback...").
- Never include changelogs, version history, "what changed" sections, or meta-commentary about the conversation, unless the user explicitly asks for a changelog as a deliverable in its own right.
- Write every section as a plain statement of fact about the current design/plan/content, as if writing it fresh with full knowledge of the final decision — not as a diff against a prior version.
- If a section documents a resolved tradeoff or an intentional design choice, state the choice and its rationale plainly (e.g. "X is an accepted tradeoff because..."), without referencing that alternatives were debated or rejected earlier in conversation.
- An "update this doc" request re-derives a clean as-is document — it does not layer edit notes onto the previous version.
When NOT to apply
- The user explicitly asks for a changelog, revision history, or "show me what changed."
- The document's entire purpose is to record a process over time — a
friction log entry (
hedgehog friction add), a commit message, or meeting notes. Those describe what happened and when on purpose.
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 · 39 lines · 85 tokens per session scan A 65dbc8e5b166
no-history-in-output is a skill published in the GitHub repository skyf0xx/hedgehog (38 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 448 once invoked, about $0.0004 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
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.