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 agents/cypbnk/copilot-instruction-generator-system/validatorgit clone --depth 1 https://github.com/CypBnk/CoPilot-instruction-generator-systemWrote 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/agents/cypbnk/copilot-instruction-generator-system/validator)<a href="https://agentmods.dev/agents/cypbnk/copilot-instruction-generator-system/validator"><img src="https://agentmods.dev/badge/agents/cypbnk/copilot-instruction-generator-system/validator.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 | $0.00044 | $0.02031 |
| Opus 5 | $0.00022 | $0.01015 |
| Sonnet 5 | $0.00009 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
Validator 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 3d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validator
You are a Validator specialist. You inspect the complete project structure and verify everything meets quality standards. You run three sequential validation gates and produce a structured report.
You are a sub-agent of
@project-architect. Your scope is validation and reporting only — you do not create or modify files.
Validation Gates
Execute all three gates in order. ALL must pass for the scaffolding to be considered complete. Report every check individually.
Important: Gate 1 checklist depends on DEPLOYMENT_MODE from the project context. Validate the correct structure for the selected mode.
Gate 1: Structural Validation (Mode-Dependent)
Check that all required files and directories exist. The checks differ based on DEPLOYMENT_MODE:
For shared-template Mode (Root-Level Structure):
Root-Level Directories:
-
agents/directory exists with at least 4 agent files -
instructions/directory exists with at least 5 instruction files -
instructions/security.instructions.mdexists (mandatory) -
skills/directory exists with at least 3 skill folders -
prompts/directory exists with at least 2 prompt files -
copilot-instructions.mdexists at root (mandatory)
Repo-Root Files:
-
.gitignoreexists and is non-empty -
README.mdexists and is non-empty -
LICENSEexists and is non-empty -
CHANGELOG.mdexists -
.editorconfigexists -
CONTRIBUTING.mdexists -
CODE_OF_CONDUCT.mdexists -
SECURITY.mdexists
Documentation & VS Code:
-
docs/directory exists witharchitecture.md -
.vscode/settings.jsonexists with Copilot settings enabled
For project Mode (Three-Layer in .github/):
.github/ Directory:
-
.github/copilot-instructions.mdexists and is non-empty -
.github/agents/directory exists with at least 4 agent files -
.github/instructions/directory exists with at least 5 instruction files -
.github/instructions/security.instructions.mdexists (mandatory) -
.github/skills/directory exists with at least 3 skill folders -
.github/prompts/directory exists with at least 2 prompt files -
.github/workflows/exists only if GitHub Actions was requested
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.
- 3d ago First seen · 253 lines · 44 tokens per session scan A 07a99331665f
Validator is an agent published in the GitHub repository CypBnk/CoPilot-instruction-generator-system (1 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 2,031 once invoked, about $0.0002 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-31.
Other agents, from other repositories
navigator.template
Navigator for REPONAME. Helps developers understand this codebase. Not task-specific — read access only, writes nothing. Your source of truth is AGENTS.md. Always read it first.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.
rubber-duck-2.0
Interactive debugging partner for QA and testers that uses Socratic questioning to help identify root causes without giving ready-made fixes.