Borrowing it
Nothing to install: this file belongs to shep-ai/shep. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shep-ai/shep/main/.claude/skills/cross-validate-artifacts/SKILL.mdgit 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/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/shep-ai/shep/cross-validate-artifacts"><img src="https://agentmods.dev/badge/skills/shep-ai/shep/cross-validate-artifacts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.5 | $0.00044 | $0.00707 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (267 stars, last pushed yesterday), licensed MIT. It adds 109 tokens to every session and 1,768 once invoked, about $0.0004 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-30.
Other skills, from other repositories
debugging-strategies
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
parallel-debugging
Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
spark-optimization
Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.