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/robotti-io/copilot-security-instructions/secure-fix-validationnpx skills add Robotti-io/copilot-security-instructions --skill secure-fix-validationgit clone --depth 1 https://github.com/Robotti-io/copilot-security-instructionsWrote 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/robotti-io/copilot-security-instructions/secure-fix-validation)<a href="https://agentmods.dev/skills/robotti-io/copilot-security-instructions/secure-fix-validation"><img src="https://agentmods.dev/badge/skills/robotti-io/copilot-security-instructions/secure-fix-validation.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.00020 | $0.00386 |
| Opus 5 | $0.00010 | $0.00193 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
secure-fix-validation 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 6d 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
Secure Fix Validation
When to use
Use this skill after implementing a security fix, or when reviewing a PR.
Inputs to collect (if available)
- Vulnerability description and expected secure behavior
- Repro steps (request, payload, or test)
- Affected components and entry points
- Deployment/rollout constraints (feature flags, backwards compatibility)
Step-by-step process
- Reproduce the issue pre-fix
- Minimal failing test or request example
- Verify the fix
- Confirm the repro now fails safely
- Regression coverage
- Add unit/integration tests for:
- expected valid inputs
- malicious/edge inputs
- authorization bypass attempts (if relevant)
- Add unit/integration tests for:
- Non-functional checks
- Error handling (no stack traces/secret leakage)
- Logging redaction (no PII/secrets)
- Performance impact in hot paths
- Rollout safety
- Feature flags where appropriate
- Backwards compatibility notes
- Monitoring/alerts to detect new failure modes
Output
- Commands run
- Tests added/updated
- Verification evidence (logs/screenshots/snippets)
- Rollout notes
Output format
- Repro (pre-fix): how it failed
- Verification (post-fix): what now happens
- Tests: added/updated + what they cover
- Evidence: logs/screenshots/snippets (redacted)
- Rollout notes: monitoring, flags, compatibility
Examples
- “Fix: block IDOR on /users/:id” → add negative test for cross-user access; verify 403 and tenant scoping on DB query.
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.
- 6d ago First seen · 57 lines · 20 tokens per session scan A 9bb91467375b
secure-fix-validation is a skill published in the GitHub repository Robotti-io/copilot-security-instructions (42 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 386 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
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent…
docs-impact-architect
Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume /…
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
example-skill
An example skill from the mock plugin.