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 bricerising/enterprise-software-playbook --skill securitygit clone --depth 1 https://github.com/bricerising/enterprise-software-playbookWrote 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/bricerising/enterprise-software-playbook/security)<a href="https://agentmods.dev/skills/bricerising/enterprise-software-playbook/security"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/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/bricerising/enterprise-software-playbook/security"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/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.00083 | $0.01644 |
| Opus 5.5 | $0.00033 | $0.00658 |
| Sonnet 5.5 | $0.00017 | $0.00329 |
| Haiku 4.5 | $0.00008 | $0.00164 |
Grade A, and why
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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security
Overview
Security is boundary discipline: authenticate, authorize, validate inputs, avoid data leakage, and make unsafe classes of bugs hard to write.
This is not a full security audit. If the change is high-risk (auth overhaul, multi-tenant isolation, crypto, payments, regulated data), escalate to a security review.
Inputs / Outputs
Inputs: Attack surface inventory (inbound/outbound/state/operational boundaries); data sensitivity classification (credentials, PII, multi-tenant identifiers).
Outputs: Hardened code with baseline controls applied (authn, authz, validation, injection safety, secrets safety); verification tests. Consumed by testing and finish.
Workflow
- Identify what changed (the attack surface):
- inbound boundaries: HTTP/gRPC/GraphQL/WS handlers, webhooks
- outbound boundaries: HTTP/gRPC/SDK clients, redirects, proxying, fetch-by-URL
- state boundaries: DB queries, object storage, caches, queues
- operational boundaries: logs/telemetry, admin endpoints, config/secrets
- Classify data sensitivity:
- credentials/secrets, session tokens, API keys
- PII and regulated data
- multi-tenant identifiers and access scopes
- Apply baseline controls:
- Authn: verify identity and token validity (issuer/audience/expiry).
- Authz: check permissions per action (and per tenant/resource).
- Input validation: treat external inputs as
unknown; decode/validate at the edge. - Injection safety: parameterize queries; avoid string-built interpreters (SQL, shell, template injection).
- Secrets safety: keep secrets out of logs, error messages, and client responses.
GATE: All 5 baseline controls (authn, authz, input validation, injection safety, secrets safety) must be addressed before proceeding. For each control, either apply it or document why it does not apply to this change.
- Harden outbound calls:
- SSRF controls (allowlist hosts; block link-local/metadata IPs; disable redirect-follow where unsafe)
- TLS verification and timeouts/cancellation (see
resilience)
- Verify:
- add/extend consumer-visible tests for authz and validation (
testing) - run any available dependency scanning / linters in the target repo
- sanity-check logs/metrics do not include sensitive fields (
observability)
- add/extend consumer-visible tests for authz and validation (
What ships with it
2 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.
- 1mo ago First seen · 117 lines · 83 tokens per session scan A fc17c57b06c1
security is a skill published in the GitHub repository bricerising/enterprise-software-playbook (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 83 tokens to every session and 1,644 once invoked, about $0.0003 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
architecture-aware-init
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
analiz-html-report
Use when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage.
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
analiz-human-review-gate
Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analizreview column.
game-engine-choice
Use when a game task could run on more than one engine or the repository has no engine yet - read the repo's engine and pinned version, and only for a brand-new game pick one from platforms, 2D/3D, team language, scale and licensing.