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/evolplus/talos/security-compliance-checklistnpx skills add evolplus/talos --skill security-compliance-checklistgit clone --depth 1 https://github.com/evolplus/talosWrote 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/evolplus/talos/security-compliance-checklist)<a href="https://agentmods.dev/skills/evolplus/talos/security-compliance-checklist"><img src="https://agentmods.dev/badge/skills/evolplus/talos/security-compliance-checklist.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.00045 | $0.00786 |
| Opus 5 | $0.00023 | $0.00393 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
security-compliance-checklist 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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security & Compliance Checklist
When to use
You are the BA. The incoming SRS describes a feature that involves at least one of: authentication, authorization, payments, PII, account data, public endpoints, or third-party integrations. CLAUDE.md §2 requires a ## Security & Compliance section in the SRS before sign-off, and this skill is the BA's playbook for what that section needs.
Inputs and outputs
- Inputs: a draft SRS with at least one trigger category present
- Outputs: a populated
## Security & Compliancesection indocs/SRS.md, plus any Open Questions for unresolved items
Trigger categories
If the SRS touches any of these, the section is mandatory:
| Trigger | Examples |
|---|---|
| Authentication | Login flows, SSO, magic links, OAuth, MFA enrollment / recovery |
| Authorization | Role checks, scope checks, resource ownership, admin endpoints |
| Payments | Card data, payment provider integrations, refunds, ledger entries |
| PII | Names, emails, phone numbers, addresses, government IDs, biometrics |
| Account data | Game progress, in-game purchases, friend lists, chat history, profile photos |
| Public endpoints | Anything reachable without auth, or with weak auth (e.g., share-by-link) |
| Third-party integrations | External APIs (payment, identity, analytics, CDN, partner game services) |
Procedure
- Read the SRS; mark every requirement that touches one of the trigger categories.
- For each marked requirement, walk the per-category checklist in
references/per-regime.md. Copy answers (or unanswered questions) into the SRS's## Security & Compliancesection. - Where the SRS is silent or ambiguous on a checklist item, raise it as
## Open Questions. Do not invent answers. - Add a final subsection
### Threats considered: 3–6 bullets naming threat actors and how the requirement addresses them. Lightweight threat-modeling, not a full STRIDE analysis. - If any item touches regional data law (Vietnam Cybersecurity Law, China data localization, Southeast Asia patchwork, GDPR for EU users), include a
### Regionalsubsection naming the regions the feature is exposed to and which constraints apply per region.
What ships with it
1 file 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.
- 5d ago First seen · 56 lines · 45 tokens per session scan A 6dd5f979833b
security-compliance-checklist is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 786 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
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…