Borrowing it
Nothing to install: this file belongs to RichardGeorgeDavis/Codex-Workspace. 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/RichardGeorgeDavis/Codex-Workspace/main/.agents/skills/security-check/SKILL.mdgit clone --depth 1 https://github.com/RichardGeorgeDavis/Codex-WorkspaceWrote 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/richardgeorgedavis/codex-workspace/security-check)<a href="https://agentmods.dev/skills/richardgeorgedavis/codex-workspace/security-check"><img src="https://agentmods.dev/badge/skills/richardgeorgedavis/codex-workspace/security-check.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.00026 | $0.00271 |
| Opus 5 | $0.00013 | $0.00135 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
security-check 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.
What it actually says
Security Check
Use this skill when a task crosses a security boundary and needs a deliberate review instead of incidental caution.
Trigger examples
- auth or session changes
- secrets or credentials
- shell execution
- file upload or file parsing
- untrusted input
- permissions or role checks
- dependency or supply-chain changes
Recommended mode handling
fast: review the highest-risk boundary onlystandard: review direct inputs, outputs, and permission checksstrict: review trust boundaries, abuse cases, and operational fallout
Working rules
- Identify the trust boundary first.
- Name the dangerous input or capability explicitly.
- Check whether the current design narrows or expands the attack surface.
- Prefer specific findings and mitigations over generic security language.
- If no issue is found, still note the reviewed boundary and residual assumptions.
Output shape
Use a compact structure such as:
- boundary reviewed
- main risks
- mitigations present
- gaps found
- follow-up checks
Non-goal
Do not turn every task into a full audit. Use this when the boundary justifies it.
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 · 47 lines · 26 tokens per session scan A 6f73f7d1179c
security-check is a skill published in the GitHub repository RichardGeorgeDavis/Codex-Workspace (2 stars, last pushed 28d ago), licensed MIT. It adds 26 tokens to every session and 271 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-31.
Other skills, from other repositories
docker-compose-local-setup
Creates or updates local multi-service orchestration using docker compose. Covers compose.yaml design, service health checks, dependson readiness, env files, named volumes, migrations/seeds jobs, verification commands, and cleanup workflows for local development.
claude-local-bridge
Access local repos from Claude on your phone via approval-gated MCP bridge.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…