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 nobrainer-tech/nobrainer-tech-skills --skill nobrainer-securitygit clone --depth 1 https://github.com/nobrainer-tech/nobrainer-tech-skillsWrote 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/nobrainer-tech/nobrainer-tech-skills/nobrainer-security)<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-security"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-security/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/nobrainer-tech/nobrainer-tech-skills/nobrainer-security"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-security.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.00051 | $0.01277 |
| Opus 5 | $0.00026 | $0.00639 |
| Sonnet 5 | $0.00010 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
nobrainer-security 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 12d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NoBrainer Security
Find exploitable security defects and missing controls in one frozen scope, then
separate proven risk from checklist noise. Default to READ_ONLY. This skill
does not authorize attacking a live target, retrieving secrets, weakening a
control, changing credentials or implementing a fix.
Choose one mode
THREAT_MODEL: map assets, actors, entry points, trust boundaries, abuse paths and required controls before a consequential design is frozen.SECURITY_REVIEW: trace an exact diff, component, endpoint or data flow and report only reachable, actionable defects.SUPPLY_CHAIN: inspect an exact dependency, installer, plugin, script, workflow or external skill for provenance, pinning, permissions and execution risk.RELEASE_GATE: verify required security controls, tests, migration safety and rollback evidence before a high-risk release.
Use nobrainer-review for a general closeout with no material security boundary.
Use nobrainer-rca when the question is what caused an observed incident.
Freeze scope and authority
Record:
MODE:
SCOPE: <exact diff/files/component/endpoint/artifact>
ASSETS_AND_DATA:
TRUST_BOUNDARIES:
ATTACKER_CAPABILITIES:
ENVIRONMENT_AND_VERSION:
WRITE_AUTHORITY: READ_ONLY unless explicitly expanded
LIVE_TEST_AUTHORITY: NONE unless exact target and actions are approved
OWNER_GATES:
Resolve actual checkout, dirty state, deployed/runtime distinction, data classification and existing controls. Never place credentials, full tokens, private payloads or exploit-ready production details in prompts or reports.
Do not test a live target, scan infrastructure, create an account, send a payload, access another user's data or install/run untrusted code without exact authorization. Prefer local fixtures, static traces and isolated reproductions.
Trace the trust boundary
Follow each relevant flow from attacker-controlled or externally supplied input through validation, canonicalization, authorization, state changes and output. For every boundary, establish:
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.
- 12d ago First seen · 151 lines · 51 tokens per session scan A f4462fef4211
nobrainer-security is a skill published in the GitHub repository nobrainer-tech/nobrainer-tech-skills (5 stars, last pushed 7d ago), licensed MIT. It adds 51 tokens to every session and 1,277 once invoked, about $0.0003 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
multi-agent-loop
Turn the current repository into a supervised multi-agent coding loop — spawn parallel AI coding agents in isolated git worktrees with file ownership, a shared radar, and human approval gates, then run the loop (status, standup, approvals) from one place.
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
collab-audit
This skill should be used when the user types /collab-audit or requests AI collaboration diagnosis. Analyzes conversation history, artifacts, and work patterns to generate a 14-section AI Collaboration Audit. Behavioral analysis and feedback are bundled by design — separating them causes users to skip one, defeating…
goal-lock
Agent Discipline Engine — lock the goal, run PLAN→DO→VERIFY→FINALIZE→OUTPUT loop, detect success masquerading. Triggers: '/goal-lock', '/goal-lock quick', 'goal lock', 'task harness'.
code-autopsy
🔬 CODE AUTOPSY v7.2 "12 Questions + Quantified + Deployment Verdict + diff mode + CRITICAL hard cap + Factuality Gate".
doc-drift
Use this skill when the user wants to audit the memory and documents Claude Code loads into context — CLAUDE.md (user global + project + nested), MEMORY.md, @imports, .claude/skills, .claude/agents, .claude/commands, installed plugins — and detect four kinds of issues: outdated claims, mutually contradictory…