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/develop-opensecret-sdknpx skills add OpenSecretCloud/Maple --skill develop-opensecret-sdkgit clone --depth 1 https://github.com/OpenSecretCloud/MapleWhat 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.00994 |
| Opus 5 | $0.00037 | $0.00497 |
| Sonnet 5 | $0.00015 | $0.00199 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
develop-opensecret-sdk 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop the OpenSecret SDK
Work from OpenSecretCloud/Maple/sdk. Read the repository-root AGENTS.md,
sdk/README.md, the affected implementation and tests, and the root
.github/workflows/sdk-*.yml files relevant to the change.
The SDK source is part of the Maple repository, but its TypeScript and Rust package boundaries remain independently versioned and publishable:
src/builds@opensecret/reactfor browser and React consumers.rust/builds theopensecretcrate for native consumers.frontend/package.jsonis authoritative for whether Maple's browser client consumes a published TypeScript version or the in-treefile:../sdkpackage.- desktop Maple and
proxy/consume the in-tree Rust crate through versioned path dependencies. iOS and Android do not compile those desktop-only consumers.
Do not commit, push, open a PR, publish, or alter Maple's application dependency wiring unless the user authorizes that action.
Keep protocol ownership clear
OpenSecret owns authentication and authorization truth, public HTTP semantics, provider policy, persistence, and usage accounting. The SDKs own client-side attestation, encrypted sessions, typed contracts, authentication state, and safe transport adaptation. Maple owns application presentation and local device behavior.
For a public contract change, inspect the exact OpenSecret backend revision and both SDK implementations when they expose the affected behavior. Preserve old-client/new-server and new-client/old-server compatibility where clients can update independently. Do not weaken HTTPS, PCR validation, attestation, key exchange, randomness, retry safety, or sanitized errors to accommodate a caller.
Develop and validate
Use the SDK's pinned Nix shell. For TypeScript/React work:
nix develop --no-update-lock-file -c bun install --frozen-lockfile --ignore-scripts
nix develop --no-update-lock-file -c bun run format:check
nix develop --no-update-lock-file -c bun run build
nix develop --no-update-lock-file -c bun test --timeout 30000
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 · 103 lines · 74 tokens per session scan A 5aada3953e21
develop-opensecret-sdk is a skill published in the GitHub repository OpenSecretCloud/Maple (91 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 994 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…