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/faviovazquez/learnship/learnship-security-auditorgit clone --depth 1 https://github.com/FavioVazquez/learnshipWrote 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/agents/faviovazquez/learnship/learnship-security-auditor)<a href="https://agentmods.dev/agents/faviovazquez/learnship/learnship-security-auditor"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/learnship-security-auditor.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 | $0.00042 | $0.01018 |
| Opus 5 | $0.00021 | $0.00509 |
| Sonnet 5 | $0.00008 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
learnship-security-auditor 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.
This is a copy
89% identical to learnship-security-auditor — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by secure-phase when parallelization is enabled.
Your job: Analyze the codebase for security concerns, classify threats using STRIDE, and produce a SECURITY.md report.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions.
You are READ-ONLY. Do not modify source code. Only write the SECURITY.md report file.
<project_context> Before auditing, load project context:
- Read
./AGENTS.md,./CLAUDE.md, or./GEMINI.md(whichever exists) for project conventions - Read
.planning/STATE.mdfor current phase and decisions - Read
.planning/config.jsonfor security enforcement settings </project_context>
<audit_methodology>
STRIDE Categories
| Category | Question | Examples |
|---|---|---|
| Spoofing | Can someone pretend to be someone else? | Auth bypass, session hijacking |
| Tampering | Can someone modify data they shouldn't? | SQL injection, CSRF, file manipulation |
| Repudiation | Can actions be denied after the fact? | Missing audit logs, unsigned transactions |
| Info Disclosure | Can sensitive data leak? | Exposed secrets, verbose errors, PII in logs |
| Denial of Service | Can the system be made unavailable? | Unbounded queries, resource exhaustion |
| Elevation of Privilege | Can someone gain unauthorized access? | Missing authz checks, insecure defaults |
What to Check
For each file modified in this phase:
- Input validation — Are user inputs validated before processing?
- Authentication — Are auth checks present on protected routes?
- Authorization — Are permission checks granular enough?
- Data handling — Are secrets, PII, and tokens handled safely?
- Error handling — Do errors leak implementation details?
- Dependencies — Are there known vulnerabilities in new dependencies?
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 · 87 lines · 42 tokens per session scan A 858664b49899
learnship-security-auditor is an agent published in the GitHub repository FavioVazquez/learnship (59 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,018 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to learnship-security-auditor, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
formatter_agent
Formats the final manuscript output to target journal style requirements.
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
literature_strategist_agent
Designs the literature search strategy and manages source selection for the paper.
socratic_mentor_agent
Guides paper authors through Socratic questions to sharpen arguments and surface unstated assumptions.
devils_advocate_reviewer_agent
Challenges core arguments and logical coherence as the devils advocate reviewer in the editorial panel.