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 skills add porcupine-md/jonggrang --skill shaping-requirementsgit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/porcupine-md/jonggrang/shaping-requirements)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/shaping-requirements"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/shaping-requirements/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/shaping-requirements"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/shaping-requirements.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00429 |
| Opus 5 | $0.00007 | $0.00215 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
shaping-requirements 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 12d 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
Shaping Requirements
Role Constraints: Lead (Write/Bash access allowed).
File Access: Do NOT use literal placeholders for file paths. Use the glob tool to search for the active feature directory under .jonggrang/.output/features/.
Methodology
Use this methodology when collaboratively shaping a solution with the user - iterating on problem definition (requirements) and solution options (shapes).
Step 1: Understand the Problem
Before suggesting any solutions, explore the problem space.
- What is the actual user struggle?
- Ask clarifying questions to dig deeper into the "why" behind the request.
- Define what is explicitly out of bounds (what we are NOT solving).
Step 2: Establish the Appetite
- How much time/effort is this problem worth? Is it a quick patch or a major feature?
- Constraint-driven design: The appetite determines the scope of the solution.
Step 3: Explore Solution Shapes
Draft rough concepts, not high-fidelity designs.
- Use natural language to describe the moving parts.
- Propose 2-3 different conceptual approaches (shapes) with tradeoffs.
- Keep it abstract enough to leave room for designers/engineers to invent, but concrete enough to know what we are building.
Step 4: Address Risks and Rabbit Holes
- What could go wrong? What are the technical unknowns?
- Call out potential "rabbit holes" where the team might get stuck.
Step 5: Write the Pitch
Use your write tool to create or update pitch.md inside the active feature directory found via glob under .jonggrang/.output/features/.
Structure the pitch with:
- Problem
- Appetite
- Solution (the shape)
- Rabbit holes
- No-gos
Completion Signal
When the shaping process is finalized and the pitch is saved, output exactly:
SHAPING_COMPLETE
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.
- 12d ago First seen · 50 lines · 14 tokens per session scan A 4b42c12b9a12
shaping-requirements is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 429 once invoked, about $0.0001 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…