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 DorianSchlede/nexus-template --skill validate-skill-functionalitygit clone --depth 1 https://github.com/DorianSchlede/nexus-templateWrote 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/dorianschlede/nexus-template/validate-skill-functionality)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/validate-skill-functionality"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/validate-skill-functionality/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/dorianschlede/nexus-template/validate-skill-functionality"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/validate-skill-functionality.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.00016 | $0.00669 |
| Opus 5 | $0.00008 | $0.00334 |
| Sonnet 5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
validate-skill-functionality 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Skill Functionality
Purpose: Systematic post-execution review to validate skill functionality and document findings.
When to Use: After a skill has completed its full execution workflow
Workflow
Follow these steps to validate skill functionality:
Step 1: Review Execution Context
- Identify which skill was just executed
- Review what the skill was supposed to accomplish
- Check the SKILL.md to understand expected behavior
- Review conversation history to identify all tool calls made during execution
Step 2: Validate File Loading
Check that all required files were loaded correctly:
- Review all Read tool calls in the conversation
- Verify SKILL.md was loaded (for skill execution context)
- Check if skill references other files (references/, scripts/, assets/)
- Confirm referenced files were actually loaded when needed
- Look for "File not found" errors or truncated reads
- Verify file paths match expected locations
Example checks:
[OK] SKILL.md loaded: Yes (line 1-88, complete)
[OK] references/workflow.md loaded: Yes (when needed in Step 2)
[ERROR] references/error-handling.md loaded: No (should have been loaded but wasn't)
[OK] scripts/bulk-complete.py executed: Yes (correct parameters)
Step 3: Validate Skill Nesting/Wrapping
Check if skills correctly loaded nested skills:
- Identify if the skill called other skills (e.g., execute-build calls create-skill)
- Verify nested skills were loaded using nexus-loader.py or explicit Read
- Confirm nested skill workflows were followed correctly
- Check that context was passed properly between skills
- Validate that nested skill outputs fed back correctly
Example checks:
Primary Skill: execute-build
[OK] Loaded: Yes (via nexus-loader.py --skill execute-build)
Nested Skill: create-skill
[OK] Loaded: Yes (via nexus-loader.py --skill create-skill)
[OK] SKILL.md read: Yes (complete)
[OK] Workflow followed: Yes (all 7 steps)
[OK] Context passed: Yes (user's workflow → create-skill)
Nested Skill: close-session
[OK] Loaded: Yes (auto-triggered)
[OK] workflow.md loaded: Yes (as required)
[OK] All 8 steps executed: Yes
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 · 91 lines · 16 tokens per session scan A 01739e7807d7
validate-skill-functionality is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 669 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.