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 odarino/haren --skill validate-artifactgit clone --depth 1 https://github.com/odarino/harenWrote 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/odarino/haren/validate-artifact)<a href="https://agentmods.dev/skills/odarino/haren/validate-artifact"><img src="https://agentmods.dev/badge/skills/odarino/haren/validate-artifact/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/odarino/haren/validate-artifact"><img src="https://agentmods.dev/badge/skills/odarino/haren/validate-artifact.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.00010 | $0.00495 |
| Opus 5 | $0.00005 | $0.00247 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
validate-artifact 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 9d 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
Validate Artifact
Verify that an artifact has all required fields and content before allowing a phase transition.
Validation Rules by Type
Context Brief (01-discovery)
Required sections:
- Project overview and goals
- Key requirements (at least 3)
- Constraints and assumptions
- Identified risks
Module Definition (02-modules)
Required fields:
- Name and description
- Responsibilities (at least 1)
- Interfaces section (can be "none" for leaf modules)
- Dependencies section
- Target repo(s)
Module Map (02-modules/module-map.md)
Required:
- All modules listed
- Dependency graph (no cycles — validate by attempting topological sort)
- Implementation order
Spec (04-plans)
Required sections:
- Requirements (functional)
- User stories with acceptance criteria
- Interface contracts
- Definition of done checklist
Design (04-plans)
Required sections:
- Architecture overview
- Data model (or "N/A" with justification)
- Key technical decisions
Tasks (04-plans)
Required:
- At least 1 task
- Each task has: title, description, files
- Tasks are ordered
Iteration-Scoped Design (04-plans, iterations only)
Iteration-scoped designs are filtered subsets of the master design. Relaxed checks:
- Architecture overview (can reference master for full detail)
- Key technical decisions relevant to this iteration's tasks
- Cross-reference to spec:
Spec: artifacts/03-modules/{module}/spec.md - Cross-reference to master design:
Master: artifacts/04-plans/{module}/design.md
Output
PASS — all required fields present
or
FAIL — missing:
- {field 1}
- {field 2}
Warnings:
- {non-blocking issue}
Rules
- FAIL blocks the phase transition — fix before proceeding
- Warnings are informational — note but don't block
- If a section says "TBD" or "TODO", that's a FAIL
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.
- 9d ago First seen · 79 lines · 10 tokens per session scan A f6fa6f265959
validate-artifact is a skill published in the GitHub repository odarino/haren (11 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 495 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…