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 ApiliumCode/mayros --skill code-securitygit clone --depth 1 https://github.com/ApiliumCode/mayrosWrote 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/apiliumcode/mayros/code-security)<a href="https://agentmods.dev/skills/apiliumcode/mayros/code-security"><img src="https://agentmods.dev/badge/skills/apiliumcode/mayros/code-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/apiliumcode/mayros/code-security"><img src="https://agentmods.dev/badge/skills/apiliumcode/mayros/code-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.00016 | $0.00478 |
| Opus 5.5 | $0.00006 | $0.00191 |
| Sonnet 5.5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
code-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.
What it actually says
code-security
Classifies code vulnerabilities by OWASP Top 10 categories and CWE identifiers, providing severity ratings for each finding.
When to Use
Use this skill when:
- Reviewing code snippets stored in the knowledge graph for security vulnerabilities
- Performing automated security audits on code content
- Classifying findings by CWE identifier and severity level before human review
Vulnerability Coverage
The skill detects 12 vulnerability classes:
| CWE | Category | Severity |
|---|---|---|
| CWE-89 | SQL Injection | critical |
| CWE-79 | Cross-Site Scripting (XSS) | high |
| CWE-78 | Command Injection | critical |
| CWE-22 | Path Traversal | high |
| CWE-502 | Insecure Deserialization | high |
| CWE-798 | Hardcoded Secrets | critical |
| CWE-95 | Code Injection | critical |
| CWE-918 | Server-Side Request Forgery (SSRF) | high |
| CWE-327 | Weak Cryptography | medium |
| CWE-601 | Open Redirect | medium |
| CWE-209 | Information Exposure | low |
| CWE-306 | Missing Authentication | medium |
Instructions
- Store code content in the graph using
skill_assertor other write tools - Query with predicate
security:findingto trigger the code-security runtime - The skill enriches each result with a
findingsarray containing CWE IDs and severity levels - Use
security:vulnerability(with proof) to record confirmed vulnerabilities - Query
security:historyto review past audit results for the current agent
What ships with it
9 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 · 60 lines · 16 tokens per session scan A 987494944bac
code-security is a skill published in the GitHub repository ApiliumCode/mayros (13 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 478 once invoked, about $0.0001 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-30.
Other skills, from other repositories
ramp
Fetch and follow Ramp's published agent playbooks inside Paperclip, with mandatory approval gates for spend, incorporation, cards, account setup, and other financial actions.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.
LLM Wiki Maintainer
Use the LLM Wiki plugin tools to maintain a cited local company wiki.
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
assimilate-popular-workflows
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…