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 sigistry/marketplace --skill security-methodologygit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/security-methodology)<a href="https://agentmods.dev/skills/sigistry/marketplace/security-methodology"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/security-methodology.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.00062 | $0.00693 |
| Opus 5 | $0.00031 | $0.00347 |
| Sonnet 5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
security-methodology 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 8d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Assessment Methodology
Purpose
Provide standardized security assessment frameworks, vulnerability classification systems, and compliance evaluation methodology for use during security scanning and auditing. Tech-agnostic, applies to any language or framework.
OWASP Risk Rating
Calculate risk using these factors:
| Risk Factor | Score (0-9) | What to Evaluate |
|---|---|---|
| Threat Agent | 0-9 | Skill level, motive, opportunity, size of threat group |
| Attack Vector | 0-9 | Ease of exploitation (automated=9, requires physical access=1) |
| Security Weakness | 0-9 | Prevalence × detectability |
| Technical Impact | 0-9 | Loss of confidentiality, integrity, availability |
| Business Impact | 0-9 | Financial, reputation, compliance, privacy damage |
Overall Risk = Average of factors, weighted by context.
Security Debt Calculation
| Severity | Remediation Time per Issue | Priority |
|---|---|---|
| Critical | 4 hours | P0, fix immediately |
| High | 2 hours | P1, fix this sprint |
| Medium | 1 hour | P2, fix this quarter |
| Low | 30 minutes | P3, fix when convenient |
Total Security Debt = Sum of (count × remediation time) per severity level.
Security Maturity Model
| Level | Name | Description |
|---|---|---|
| 0 | None | No security measures |
| 1 | Initial | Ad-hoc, reactive security |
| 2 | Managed | Basic security controls in place |
| 3 | Defined | Standardized security processes |
| 4 | Quantified | Metrics-driven security decisions |
| 5 | Optimizing | Continuous security improvement |
Security Score Breakdown
Rate each dimension 0-10:
| Dimension | What to Evaluate |
|---|---|
| Authentication & Authorization | Auth mechanisms, RBAC/ABAC, session management |
| Data Protection | Encryption at rest/transit, data masking, PII handling |
| Input Validation | Sanitization, whitelisting, encoding at boundaries |
| Cryptography | Algorithm strength, key management, randomness |
| Session Management | Token handling, timeout, fixation prevention |
| Error Handling | Information leakage, stack traces, debug exposure |
| Dependency Security | CVE count, update frequency, vulnerable transitive deps |
| Configuration Security | Default credentials, debug mode, unnecessary services |
What ships with it
4 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.
- 8d ago First seen · 72 lines · 62 tokens per session scan A 2fc9fd874de6
security-methodology is a skill published in the GitHub repository sigistry/marketplace (3 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 693 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
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
cold-start-problem
Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my…
37signals-way
Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat…
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
root-cause-investigator
Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.