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 paruff/uFawkesAI --skill integritygit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/integrity)<a href="https://agentmods.dev/skills/paruff/ufawkesai/integrity"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/integrity/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/paruff/ufawkesai/integrity"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/integrity.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.00028 | $0.00530 |
| Opus 5 | $0.00014 | $0.00265 |
| Sonnet 5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
artifact-integrity-validation 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.
What it actually says
Skill: Artifact Integrity Validation
Load trigger:
"load artifact-integrity-validation skill"> DORA: Cap 1 (AI Policy) Token cost: Low
Purpose
Ensure all build artifacts are tamper-proof and verifiable.
Responsibilities
- Validate checksums
- Validate signatures
- Validate provenance
Inputs
- Build artifacts
Outputs
integrity.json
Artifact Types
| Artifact | Checksum | Signature | Provenance |
|---|---|---|---|
| Container image | digest | Cosign | SLSA |
| SBOM | sha256 | Cosign | - |
| Manifests | sha256 | - | - |
| Binaries | sha256 | Cosign | SLSA |
Validation Commands
# Checksum
sha256sum artifact > artifact.sha256
sha256sum -c artifact.sha256
# Signature
cosign verify-blob --signature artifact.sig --cert artifact.cert artifact
# Provenance
cosign verify-attestation --type slsaprovenance --key cosign.pub artifact
Validation Rules
- All artifacts have checksums
- All checksums valid
- All signatures valid
- Provenance attached where required
- No tampering detected
Output Format
{
"skill": "artifact-integrity-validation",
"status": "pass | fail",
"artifacts": [
{
"name": "my-app:v1.3.0",
"checksum": "valid",
"signature": "valid",
"provenance": "valid"
},
{
"name": "sbom.json",
"checksum": "valid",
"signature": "valid",
"provenance": "n/a"
}
],
"total_artifacts": 5,
"verified": 5,
"failed": 0
}
Success Criteria
- All artifacts integrity-verified
- No tampering detected
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 First seen · 95 lines · 28 tokens per session scan A 0aa67c643fb8
artifact-integrity-validation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 28 tokens to every session and 530 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
infrastructure-validation
Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.
template-academic-paper
Template-native manuscript planning, outline, drafting, revision, formatting, citation check, and AI-use disclosure routing. USE WHEN the user asks to write, outline, revise, format, or prepare a paper inside the Research Project Template.
infrastructure-llm
Skill for the LLM infrastructure module providing local Large Language Model integration via Ollama. Covers client initialization, prompt templates, output validation, manuscript review generation, conversation context, and CLI usage. Use when querying LLMs, generating manuscript reviews, validating LLM outputs, or…
research-workflow
Seven-stage research workflow (SCOPE→LITERATURE→REASON→DESIGN→COMPUTE→SYNTHESIZE→WRITE). Use for: structuring an AI agent's research process, generating literature review prompts, scoping methodology. Usage: from infrastructure.research import ResearchWorkflow; ResearchWorkflow.describe() Config: set stage overrides…