Borrowing it
Nothing to install: this file belongs to mazumba/opencode-dockerized. 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/mazumba/opencode-dockerized/main/.opencode/config/skills/security-core/SKILL.mdgit clone --depth 1 https://github.com/mazumba/opencode-dockerizedWrote 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/mazumba/opencode-dockerized/security-core)<a href="https://agentmods.dev/skills/mazumba/opencode-dockerized/security-core"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/security-core/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/mazumba/opencode-dockerized/security-core"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/security-core.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01010 |
| Opus 5.5 | $0.00015 | $0.00404 |
| Sonnet 5.5 | $0.00007 | $0.00202 |
| Haiku 4.5 | $0.00004 | $0.00101 |
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 24d 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 — 89 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.
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 |
| Control Area | Minimum Expectation | Frequent Failure Mode |
|---|---|---|
| Threat modeling | Assets, actors, trust boundaries, abuse cases are explicit | Focus on features, skip attacker paths |
| Dependency/supply-chain | Lockfiles, provenance checks, vulnerability triage SLA | Unpinned transitive updates, ignored advisories |
| Auth/Authz | Strong authN, server-side authZ, deny-by-default policy | Client-side-only checks, role drift |
| Input validation | Centralized allowlist validation and output encoding | Validation only at edge, inconsistent schemas |
| Secrets/config | No hardcoded secrets, env isolation, rotation metadata | Secrets in logs/repos, shared credentials |
| Logging/alerting | Structured security events with actionable alert routing | Missing actor/context, noisy unactionable alerts |
| Disclosure readiness | Public reporting channel and coordinated response template | No owner, ad hoc communication |
What ships with it
7 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.
- 24d ago Changed · -14 lines · +5 tokens per session fb71b78a3f0d
- 1mo ago First seen · 103 lines · 32 tokens per session scan A a7b94ee1b5e8
security-core is a skill published in the GitHub repository mazumba/opencode-dockerized (6 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,010 once invoked, about $0.0001 per session on Opus 5.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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.