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 agentmods add skills/shep-ai/shep/cross-validate-artifactsnpx skills add shep-ai/shep --skill cross-validate-artifactsgit clone --depth 1 https://github.com/shep-ai/shepWrote 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/shep-ai/shep/cross-validate-artifacts)<a href="https://agentmods.dev/skills/shep-ai/shep/cross-validate-artifacts"><img src="https://agentmods.dev/badge/skills/shep-ai/shep/cross-validate-artifacts.svg" alt="Measured on agentmods" 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.00109 | $0.01768 |
| Opus 5 | $0.00055 | $0.00884 |
| Sonnet 5 | $0.00022 | $0.00354 |
| Haiku 4.5 | $0.00011 | $0.00177 |
Grade A, and why
cross-validate-artifacts 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Validate Artifacts Skill
Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions.
Trigger
Use this skill when the user:
- Asks to "cross-validate", "validate docs", "check documentation consistency"
- Wants to find conflicts or contradictions in documentation
- Asks to audit or review documentation for accuracy
- Uses
/cross-validate-artifactscommand
Arguments
- No arguments: Perform validation and present results summary table, then ask user if they want to fix
validate and fixorfix: Perform validation AND automatically fix all issues found--category <name>: Validate specific category only (domain-models, agent-system, tech-stack, architecture, cli-commands)
Validation Process
Step 1: Identify Documentation Sources
Gather all documentation files to validate:
Root docs:
- README.md
- CLAUDE.md
- AGENTS.md
- CONTRIBUTING.md
docs/ folder:
- docs/architecture/*.md
- docs/concepts/*.md
- docs/guides/*.md
- docs/development/*.md
- docs/api/*.md
Step 2: Break Into Validation Categories
Split validation into parallel sub-tasks for efficiency. Each category should be handled by a dedicated subagent:
| Category | Description | Key Files to Compare |
|---|---|---|
| domain-models | Entity definitions, fields, enums | CLAUDE.md, docs/api/domain-models.md, docs/concepts/*.md |
| agent-system | Agent names, tools, state schema, workflow | AGENTS.md, docs/architecture/agent-system.md, docs/guides/langgraph-agents.md |
| tech-stack | Framework versions, library references | README.md, CLAUDE.md, docs/architecture/overview.md |
| architecture | Layer descriptions, folder structure, patterns | CLAUDE.md, docs/architecture/*.md, CONTRIBUTING.md |
| cli-commands | pnpm scripts, paths, configuration | CLAUDE.md, docs/development/.md, docs/guides/.md |
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.
- 5d ago First seen · 228 lines · 109 tokens per session scan A 44a7005f38f4
cross-validate-artifacts is a skill published in the GitHub repository shep-ai/shep (247 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 1,768 once invoked, about $0.0005 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
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.