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 skills/opensecretcloud/maple/review-maple-securitynpx skills add OpenSecretCloud/Maple --skill review-maple-securitygit clone --depth 1 https://github.com/OpenSecretCloud/MapleWrote 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/opensecretcloud/maple/review-maple-security)<a href="https://agentmods.dev/skills/opensecretcloud/maple/review-maple-security"><img src="https://agentmods.dev/badge/skills/opensecretcloud/maple/review-maple-security.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.00074 | $0.05422 |
| Opus 5 | $0.00037 | $0.02711 |
| Sonnet 5 | $0.00015 | $0.01084 |
| Haiku 4.5 | $0.00007 | $0.00542 |
Grade A, and why
review-maple-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 4d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Maple Security
Review the current source, not remembered findings. Separate policy, consent, containment, and server authorization. Treat Maple as an open-source client of OpenSecret; discuss billing and feature flags only through their public API/configuration contracts.
Default to read-only investigation when asked to review, audit, diagnose, or threat-model. Do not implement, commit, push, open issues, or make incident claims unless the user separately authorizes the relevant action and the evidence supports it.
Establish the Review Baseline
-
Read
AGENTS.md, the requested diff or files, nearby tests, and applicable docs. -
Record
git status --short --branch,git rev-parse HEAD, the comparison base, and whether the checkout has unrelated changes. Never clean or rewrite them. -
Re-check current command and dependency sources:
justfile,frontend/package.json,frontend/src-tauri/Cargo.toml, lockfiles,scripts/ci/, and.github/workflows/. -
Identify whether the request is:
- a read-only audit of current behavior;
- a review of a bounded diff;
- a proposed security design; or
- validation of an implemented fix.
-
State the assets, attacker position, trust boundaries, and deployment assumptions before assigning severity.
Do not infer deployment state from repository source. Do not infer runtime behavior from a passing build. Do not infer authorization from hidden UI or a feature flag.
Use an Evidence Taxonomy
Label every material claim with the strongest evidence actually obtained:
- Source-confirmed: current checked-out code directly implements the behavior.
- Test-confirmed: a focused or full automated test exercised the behavior.
- Runtime-confirmed: the exact web or native application demonstrated it locally.
- Deployment-confirmed: the relevant deployed service, policy, or artifact was inspected.
- Inferred risk: the consequence follows from confirmed primitives, but the full exploit path was not demonstrated.
- Unverified: a required dependency, platform, deployment, or attacker precondition was not inspected.
What ships with it
1 file 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.
- 4d ago First seen · 392 lines · 74 tokens per session scan A b39c51e0bc3b
review-maple-security is a skill published in the GitHub repository OpenSecretCloud/Maple (91 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 5,422 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…