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 HoangNguyen0403/agent-skills-standard --skill common-protocol-enforcementgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-protocol-enforcement)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-protocol-enforcement"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-protocol-enforcement/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/hoangnguyen0403/agent-skills-standard/common-protocol-enforcement"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-protocol-enforcement.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.00047 | $0.00614 |
| Opus 5 | $0.00023 | $0.00307 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
common-protocol-enforcement 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 13d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocol Enforcement (Red-Team Verification)
Priority: P0 (CRITICAL)
Red-Team Verification Protocol
Before declaring any task "done" or calling notify_user:
- Adversarial Audit: Search for Standard Defaults where project rules should exist.
- Protocol Check: Confirm active skills and workflows were loaded before writing.
- Evidence Check: Ask what command or artifact proves the completion claim.
- Execution Bias Check: Ask whether speed or convenience skipped a structural rule.
** Post-Write Self-Scan**
Immediately after tool call:
- Scan: Read diff or file content.
- Match: Check against
Anti-Patternsin all active skills. - Fix: Re-edit immediately if violation detected.
Red Flags
- Stop if "done" appears before fresh verification: No completion claim yet.
- Stop if you relied on memory instead of re-reading files: Reload source of truth.
- Stop if the shortcut is "small enough to skip protocol": Small changes hide drift.
Rationalization Prevention
- "The change is tiny": Tiny changes still violate guardrails.
- "The test passed earlier": Old evidence does not prove current state.
- "I know the pattern already": Load the active skill anyway.
Anti-Patterns
- No "Done" Bias: Functional success != Protocol success.
- No Reliance on Memory: Always retrieval-led (Skill view_file) before write.
- No Skipping Protocols: "Small changes" where most violations happen.
Execution Bias Detection
Look for:
- Local mocks instead of shared fakes.
- Hardcoded styles instead of design tokens.
- Try-catch blocks without standard error handling.
- Missing
Pre-Write Audit Login thoughts.
References
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
-
active skill
-
active skills
-
reload
-
Additional task-grounded exact anchors: Pre-Write Audit; Standard Defaults; Anti-Patterns
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.
- 13d ago First seen · 82 lines · 47 tokens per session scan A 35c6689dd049
common-protocol-enforcement is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 614 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-30.
Other skills, from other repositories
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
testing
Skill "testing" from udecode/plate-playground-template, covering testing goal, core rules, seam selection, fixtures and assertions and quick reference.
playtest
Drive a real browser against a game with vg playtest: smoke checks, scripted bot playtests, softlock detection, screenshots and visual diffs, on localhost or a deployed URL.
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.
nextjs-development
Next.js 16.2.4 with TypeScript — App Router, Server Components, use cache directive, Turbopack dev, Server Actions, ISR, SSR, SSG, MCP devtools, metadata API, route handlers, instrumentation.