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/mazumba/opencode-dockerized/security-corenpx skills add mazumba/opencode-dockerized --skill security-coregit clone --depth 1 https://github.com/mazumba/opencode-dockerizedWhat 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.00032 | $0.01158 |
| Opus 5 | $0.00016 | $0.00579 |
| Sonnet 5 | $0.00006 | $0.00232 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
security-core 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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: security-core
Overview
Application security core covers baseline risk discovery and control verification across architecture, code, dependencies, runtime configuration, and operational response. It includes threat modeling, identity and access checks, input handling controls, secret management hygiene, and monitoring/disclosure readiness. The domain focuses on reducing exploitability and blast radius while improving detection and recovery quality.
File & Directory Map
| Path | Purpose |
|---|---|
SKILL.md |
This reference file |
GOTCHAS.md |
Known failure points and fixes |
HISTORY.md |
Append-only change log |
assets/ |
Shared templates and output scaffolds |
assets/finding-template.json |
Canonical finding output schema |
assets/threat-model-template.md |
Lightweight threat model snapshot template |
assets/disclosure-intake-template.md |
Coordinated disclosure intake template |
assets/remediation-tracker-template.csv |
Remediation tracking starter sheet |
scripts/ |
Helper scripts and libraries the agent can run or compose (if any) |
Key Facts
- This skill is defensive-only. It is for risk discovery, validation, mitigation planning, and response readiness; it is not for exploit development, payload design, or offensive operation support.
- Scope is baseline controls reusable across repositories; project-specific enforcement and stack details belong in a companion
security-profileskill per repository. - Security review scope commonly spans design-time, build-time, deploy-time, and runtime controls; missing any layer creates false confidence.
- Severity language should be stable across findings:
critical,high,medium,low,informational; include bothimpactandlikelihoodrationale. - Prefer explicit trust boundaries and data-flow labels for threat models:
external,partner,internal,privileged,regulated.
| Severity | Impact Guide | Likelihood Guide | Typical SLA Target |
|---|---|---|---|
critical |
Immediate compromise of sensitive systems/data | Active abuse or trivial path | Same day |
high |
Significant data, auth, or integrity impact | Realistic exploit path | 7 days |
medium |
Scoped impact or strong preconditions | Possible with constraints | 30 days |
low |
Limited impact, defense-in-depth gap | Unlikely or narrow | 90 days |
informational |
No direct exploit impact | N/A | Backlog |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 103 lines · 32 tokens per session scan A a7b94ee1b5e8
security-core is a skill published in the GitHub repository mazumba/opencode-dockerized (5 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 1,158 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…