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 artvepa80/Agents-Hefesto --skill analysisgit clone --depth 1 https://github.com/artvepa80/Agents-HefestoWrote 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/artvepa80/agents-hefesto/analysis)<a href="https://agentmods.dev/skills/artvepa80/agents-hefesto/analysis"><img src="https://agentmods.dev/badge/skills/artvepa80/agents-hefesto/analysis/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/artvepa80/agents-hefesto/analysis"><img src="https://agentmods.dev/badge/skills/artvepa80/agents-hefesto/analysis.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.00056 | $0.00365 |
| Opus 5.5 | $0.00022 | $0.00146 |
| Sonnet 5.5 | $0.00011 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
HefestoAI Output Analysis 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 20d 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
Interpret HefestoAI output
Activate after any hefesto analyze run (any exit code), after the pre-commit
hook, after CI gate results, or when the user asks what Hefesto found.
Quick reference
- Exit codes:
0clean ·1gate failure / error ·2drift threshold - Formats:
--output text(default),--output json,--output html - Gate:
--fail-on HIGHexits1if any HIGH+ issues
Workflow
hefesto analyze . --output json --fail-on HIGH
→ parse JSON (interpret_output.md)
→ fix suggestions (fix_suggestions.md)
→ commit quality report (report_template.md)
→ optional HERMES staging (hermes_integration.md)
Progressive docs
| File | Purpose |
|---|---|
| interpret_output.md | Parse text/JSON fields |
| fix_suggestions.md | Fixes by category |
| report_template.md | Commit quality report |
| hermes_integration.md | HERMES content pipeline |
Rules
- Quote severities and issue codes from the actual output; do not invent findings.
- If exit code is non-zero, do not recommend committing until fixed or the user overrides.
What ships with it
5 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.
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.
- 20d ago Changed · -3 lines · +56 tokens per session 7ee46081a442
- 1mo ago First seen · 46 lines · 0 tokens per session scan A f3795aed80f5
HefestoAI Output Analysis is a skill published in the GitHub repository artvepa80/Agents-Hefesto (7 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 365 once invoked, about $0.0002 per session on Opus 5.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
ai-debt-audit
Scan a repository for AI-generated technical, cognitive, and intent debt. Use when the user asks to audit a codebase for AI/vibe-coding risk, check for issues an AI coding assistant may have introduced (disabled RLS, hardcoded secrets, missing auth checks, SSTI, debug mode left on), assess technical debt after heavy…
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…
argot-write-rule
Codify a repo convention argot's built-ins don't cover into a scripted custom rule — a .argot/rules/NAME/rule.toml manifest plus a sandboxed Rhai script that fires exactly like a built-in, gated on a green fixture suite before it ever sees a real diff. Use when the user asks to "write an argot rule for X", "codify…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.
poly-lint-and-format
Running poly lint / poly fmt — --fix, --format pretty|json|toon, --exclude, --config, exit codes, inline suppression, and the check → read-json → fix → re-check loop.
poly-tiers-and-scope
Five mechanisms decide what actually inspects a file (crates/poly-core/src/registry.rs).