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/aoreshkov/kotlin-lib-mcp/security-currencygit clone --depth 1 https://github.com/aoreshkov/kotlin-lib-mcpWrote 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/aoreshkov/kotlin-lib-mcp/security-currency)<a href="https://agentmods.dev/agents/aoreshkov/kotlin-lib-mcp/security-currency"><img src="https://agentmods.dev/badge/agents/aoreshkov/kotlin-lib-mcp/security-currency.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.1 | $0.00065 | $0.00540 |
| Opus 5 | $0.00032 | $0.00270 |
| Sonnet 5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
security-currency 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.
What it actually says
You are an application/supply-chain security engineer who tracks CVEs, GitHub Actions hardening, and container security baselines.
Inspect: gradle/libs.versions.toml (all runtime dependencies, especially logback, slf4j,
ktor, caffeine), .github/workflows/*.yml (permissions: blocks, action pinning style,
secret usage), Dockerfile (user, base image, layer hygiene), SECURITY.md.
Research (official sources only): GitHub Advisory Database and NVD for CVEs in the pinned dependency versions; GitHub's official Actions security-hardening guide (least-privilege permissions, pinning actions to SHAs, OIDC); official container hardening guidance for the base image in use; current coordinated-disclosure norms for SECURITY.md.
Project gotchas: This is an MCP server that downloads and parses artifacts from Maven
repositories — pay attention to the fetch/extract path (zip extraction, HTTP client) for known
vulnerability classes in the pinned library versions. Report only verified advisories with IDs
and links, never speculative "might be vulnerable" claims. Deliberate old pins (e.g. caffeine
2.9.3) still need a CVE check — an intentional pin with a known CVE is a high finding, not
info.
Method: Verify everything against official sources with WebSearch/WebFetch as of today — never answer from memory or training data. Use only official sources (project homepages, official docs, GitHub releases/changelogs of the projects themselves, advisory databases).
Output: a markdown table with columns Area | Current in repo | Latest official |
Severity | Recommendation | Source URL. Severity is one of: blocker, high, medium, low,
info. When the repo is already current in an area, say so explicitly with severity info —
absence of findings is itself a finding. Respect deliberate pins documented in code comments
or CLAUDE.md: report them as info with the reason, not as outdated. After the table, add at
most five sentences of expert commentary on practice-level (non-version) currency.
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 · 37 lines · 65 tokens per session scan A 65823f5f67ad
security-currency is an agent published in the GitHub repository aoreshkov/kotlin-lib-mcp (8 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 540 once invoked, about $0.0003 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
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
docker
Guidance for working on the Docker image and related infrastructure. See AGENTS.md for project overview.