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 commands/srstomp/pokayokay/securitygit clone --depth 1 https://github.com/srstomp/pokayokayWhat 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 | $0.00007 | $0.00934 |
| Opus 5 | $0.00003 | $0.00467 |
| Sonnet 5 | $0.00001 | $0.00187 |
| Haiku 4.5 | $0.00001 | $0.00093 |
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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit Workflow
Security audit: $ARGUMENTS
Agent Delegation
Delegate the security scanning to the yokay-security-scanner agent for isolated execution. This keeps verbose scan output separate and enforces read-only constraints.
Use the yokay-security-scanner agent to scan: $ARGUMENTS
Return the severity summary and critical/high findings to this conversation.
The agent will:
- Scan for OWASP Top 10 vulnerabilities
- Check for secrets exposure, injection risks, XSS
- Review authentication/authorization patterns
- Return findings classified by severity (Critical/High/Medium/Low)
After receiving the agent's findings, continue with remediation task creation below.
Steps
1. Define Audit Scope
From $ARGUMENTS, identify:
- Code audit: Specific files/components
- Dependency audit: npm/pip packages
- Configuration audit: Environment, secrets, infra
- Architecture audit: Authentication, authorization flows
2. Run Automated Scans
# Dependency vulnerabilities
npm audit
# or
pnpm audit
# Secret detection
git secrets --scan
3. Manual Review Checklist
OWASP Top 10:
- Injection (SQL, NoSQL, OS commands)
- Broken authentication
- Sensitive data exposure
- XML external entities (XXE)
- Broken access control
- Security misconfiguration
- Cross-site scripting (XSS)
- Insecure deserialization
- Components with known vulnerabilities
- Insufficient logging/monitoring
4. Classify Findings
| Severity | Description | Action |
|---|---|---|
| Critical | Immediate exploit risk | Fix now |
| High | Significant vulnerability | Fix this sprint |
| Medium | Moderate risk | Plan fix |
| Low | Minor issue | Backlog |
| Info | Best practice | Consider |
5. Generate Report
Document findings with:
- Vulnerability description
- Location (file:line)
- Severity and CVSS score
- Remediation steps
- References (CWE, CVE)
6. Create Remediation Tasks
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.
- 2d ago First seen · 135 lines · 7 tokens per session scan A 7527615a56a1
security is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 934 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.