What is develop-maple?

A set of instructions for developing and debugging ordinary Maple features across its React/Vite interface and Tauri/Rust application. It covers setup, frontend and native changes, desktop and mobile work, testing, and routing specialized tasks.

Use it for normal Maple UI, state, API-client, native-command, desktop, and mobile changes, plus focused tests and preparation for validation.

It helps developers choose the correct part of the application for a change and use the project’s authoritative setup and validation commands. It also directs security-sensitive or specialized work to the relevant instructions.

develop-maple — Skill by OpenSecretCloud

Install

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.

agentmods

npx agentmods add skills/opensecretcloud/maple/develop-maple

Any agent

npx skills add OpenSecretCloud/Maple --skill develop-maple

Clone the repo

git clone --depth 1 https://github.com/OpenSecretCloud/Maple

Made for: Claude Code, Codex.

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,787 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00093	$0.01787
Opus 5	$0.00046	$0.00894
Sonnet 5	$0.00019	$0.00357
Haiku 4.5	$0.00009	$0.00179

Measured 2d ago against content hash 0a195050e824, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

develop-maple 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.

.agents/skills/develop-maple/SKILL.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Develop Maple

Work from the OpenSecretCloud/Maple repository root. Treat justfile, frontend/package.json, flake.nix, scripts/ci/, and .github/workflows/ as the command sources of truth. Check them again when they disagree with prose documentation.

Route Specialized Work

Use $validate-maple for full validation, packaged-app smoke tests, cross-platform builds, or release-artifact verification.
Use $review-maple-security for security audits or changes involving authentication, authorization, attestation, OAuth/deep links, credentials, storage, CSP, local proxy exposure, filesystem/shell access, or trust boundaries.
Use $change-maple-agent-mode for Goose, Agent Mode runtime/UI, tool permissions, MCP, ACP, subagents, or agent persistence.
Use $develop-opensecret-sdk for changes to the TypeScript/React or Rust SDK source under sdk/, including its backend integration revision or package boundaries.
Use $develop-maple-proxy for changes to the proxy crate, standalone binary, container, or public OpenAI-compatible behavior under proxy/.
Use $release-maple for version bumps, tags, publishing, release CI, or distribution. Never use just release during ordinary development.

Keep the current task scoped when one of these skills is unnecessary. Do not claim specialized validation that was not run.

Establish a Safe Baseline

Inspect git status --short --branch, the current branch, and recent history.
Preserve all existing changes. Never reset, overwrite, or reformat unrelated work.
For newly requested isolated work, base it on current origin/master unless the user specifies another base. Do not switch branches over a dirty checkout.
Read root AGENTS.md, relevant docs, nearby implementation, tests, and current dependency/API versions before designing the change.
State the intended behavior and the smallest affected boundary before editing.

Do not commit, push, open a PR, merge, tag, publish, or release unless the user explicitly requests that action.

Read the full file on GitHub · 158 lines

Files

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.

agents/openai.yaml 186 B

Changes

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 · 158 lines · 93 tokens per session scan A 0a195050e824

Subscribe to this mod's changes

develop-maple is a skill published in the GitHub repository OpenSecretCloud/Maple (91 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 1,787 once invoked, about $0.0005 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.

Debugging Frontend Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens