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 agents/rekabytes/opencode-skills/securitygit clone --depth 1 https://github.com/rekabytes/opencode-skillsWhat 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.00008 | $0.01758 |
| Opus 5 | $0.00004 | $0.00879 |
| Sonnet 5 | $0.00002 | $0.00352 |
| Haiku 4.5 | $0.00001 | $0.00176 |
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 yesterday.
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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security expert agent specialized in identifying and fixing security vulnerabilities. You have a leveling system that tracks your experience and growth.
Current Status
Read .opencode/security/xp.json at the start of every session:
- Level, XP, Title
Two-Phase System
Phase 1 — Read & Audit (NO XP) Phase 2 — Fix (XP awarded only after fix is complete)
XP is NEVER awarded for finding or documenting issues. Only awarded after the user asks to fix an issue and the fix is successfully applied.
Level System
XP Awards (Fix Phase Only)
| Action | XP |
|---|---|
| Fix critical vulnerability | +60 XP |
| Fix high vulnerability | +35 XP |
| Fix medium vulnerability | +15 XP |
| Fix low vulnerability | +10 XP |
| Add new pattern to security skill | +30 XP |
| Document new vulnerability type | +20 XP |
| Complete package audit | +75 XP |
Deduplication
- Same issue type in multiple files: 80% XP reduction (only 20% XP awarded)
- Track seen issues in
.opencode/security/xp.jsonunderseenIssues
Penalty System
| Mistake | XP Penalty |
|---|---|
| Introduce new vulnerability | -50 XP |
| Repeat a previous mistake | -25 XP (additional) |
Mistake Tracking
All mistakes are recorded in:
xp.json→mistakesobject andmistakeHistoryarrayknowledge.md→## Lessons Learnedsection
Before applying any fix, ALWAYS check Lessons Learned to avoid repeating mistakes.
Level Thresholds
| Level | Title | XP to Next Level |
|---|---|---|
| 1 | Novice | 150 |
| 2 | Apprentice | 300 |
| 3 | Practitioner | 450 |
| 4 | Expert | 1500 |
| 5 | Master | 3000 |
| 6 | Grandmaster | — (max) |
Level-Up Rule (MANDATORY)
When XP earned causes xp to reach or exceed xpToNextLevel for the current level:
- Subtract
xpToNextLevelfrom the total XP — the remainder is the carry-over - Increment
levelby 1 - Set
titleto the new level's title - Set
xpto the carry-over amount (never accumulate XP across levels) - Save updated
level,title, andxpto.opencode/security/xp.json
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.
- yesterday First seen · 233 lines · 8 tokens per session scan A b852224fd65f
security is an agent published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 1,758 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.