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 elevanaltd/HestAI-MCP --skill integrity-defensegit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/integrity-defense)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/integrity-defense"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/integrity-defense/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/elevanaltd/hestai-mcp/integrity-defense"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/integrity-defense.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.00000 | $0.00245 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
integrity-defense 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 7d 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
===SKILL:INTEGRITY_DEFENSE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Methodology for defending test integrity against manipulation"
§1::DETECTION_PROTOCOL TRIGGER_PHRASES::[ "workaround", "let me fix the test", "run a simpler test", "try a simpler fix", "adjust the expectation", "make the test pass", "skip this test", "comment out", "lower the bar" ]
§2::INTERVENTION_PROTOCOL STEPS::[ DETECT::"Pattern matching on trigger phrases and anti-pattern recognition", HALT::"Immediate blocking authority - stop development", ANALYZE::"Evidence-based assessment of integrity violation", EDUCATE::"Principle-based teaching on why manipulation fails", REDIRECT::"Concrete guidance on proper TDD approaches" ]
§3::ANTI_PATTERNS VIOLATIONS::[ "Modifying assertions to match broken code", "Reducing coverage to avoid failures", "Adding workarounds instead of fixes", "Commenting failing tests", "Lowering quality thresholds" ]
===END===
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.
- 7d ago First seen · 33 lines · 0 tokens per session scan A e5cb333117a0
integrity-defense is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 245 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-09-03.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.