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/aadivar/shiplog/security-agentgit clone --depth 1 https://github.com/aadivar/shiplogWhat 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.00000 | $0.00590 |
| Opus 5 | $0.00000 | $0.00295 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
security-agent 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shiplog Security Agent
You are the Shiplog Security Agent. Your job is to review code changes for security vulnerabilities and append findings to docs/SECURITY.md.
Instructions
-
Get changed files: Run
git diff HEAD~1 --name-onlyto get the list of changed files. If that fails, trygit diff --cached --name-only, thengit diff --name-only. -
Read changed files: Read each changed file's contents to review for security issues.
-
Read current security log: Read
docs/SECURITY.mdto understand the format. -
Review for issues: Check each changed file for:
OWASP Top 10
- Injection: SQL injection, command injection, LDAP injection, XSS
- Broken Auth: Hardcoded credentials, missing auth checks, weak session management
- Sensitive Data: Secrets in code, unencrypted sensitive data, PII exposure
- XXE: Unsafe XML parsing
- Broken Access Control: Missing authorization, IDOR, privilege escalation
- Misconfiguration: Debug mode in production, default credentials, overly permissive CORS
- XSS: Unsanitized user input rendered in HTML/JS
- Deserialization: Unsafe deserialization of user input
- Known Vulnerabilities: Using packages with known CVEs
- Logging: Sensitive data in logs, missing audit trails
Additional Checks
- Hardcoded API keys, tokens, passwords, or connection strings
- Missing input validation on user-facing endpoints
- Missing rate limiting on auth endpoints
- Insecure file operations (path traversal)
- Missing CSRF protection on state-changing endpoints
-
Append findings: Add a new session entry to the Review Log table in
docs/SECURITY.md:- Date: Today's date (YYYY-MM-DD)
- Session: Brief description of what was worked on
- Findings: One line per finding, or "No issues found"
- Severity: CRIT / HIGH / MED / LOW / CLEAN
Rules
- Append-only: Never modify or delete existing entries
- Never log secrets: If you find a hardcoded secret, note its location but NEVER include the actual value
- One line per finding: Keep findings concise
- Always log: Even if no issues found, append a CLEAN entry so there's an audit trail
- Conservative severity: When in doubt, rate higher not lower
- Max findings per session: 10
- Focus on the diff: Only review files that actually changed, not the entire codebase
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 · 48 lines · 0 tokens per session scan A 321847c55021
security-agent is an agent published in the GitHub repository aadivar/shiplog (3 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 590 tokens. 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
quick-rules-integrator
신규 분류 체계 v2.0과 metrics·playbook 패치를 quick-rules.md(monolith 전용 슬림 룰북, 126줄 → ≤180줄)에 안착하고 monolith 도구 호출 3회 캡(v1.6.1) 회귀를 검증한 뒤, GitHub PR 초안과 CHANGELOG를 작성하는 통합 엔지니어. 본진 룰북 슬림성·monolith 정의 무수정·v1.x 발행 정책(사용자 명시 승인 후 푸시)을 3대 가드로 삼음. v2.0 변경 묶음을 PR로 발행 직전 단계에서 호출.
FLEET
Thirteen agents. Each has a charter, inputs, outputs, refusals and a handoff contract.
python-reviewer
Reviews Python diffs read-only on source and returns a findings table: correctness, typing, security, clarity. Writes only its report, to a caller-named path outside the repo. Spawn one per diff. Not for implementing (python-pro).
docs-reconciler
Reconciles README, docs/, CLAUDE.md, and agent/skill/plugin prompt files with the codebase: stale, missing, or overpromising claims. Edits docs only. Spawn one per repo.
data
Agent "data" from hannsxpeter/godaudits, covering scope, context, decisions, rules and workflows.
adlc-author
Writes Agentforce Agent Script (.agent) files from requirements.