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 scaffold-webappgit 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/scaffold-webapp)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/scaffold-webapp"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/scaffold-webapp/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/scaffold-webapp"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/scaffold-webapp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00715 |
| Opus 5.5 | $0.00008 | $0.00286 |
| Sonnet 5.5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
scaffold-webapp 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Project {{project_name}} is a web app using {{stack}}. You will create a new page "{{input.name}}" at route "{{input.route}}".
Read AGENTS.md for conventions. Read existing pages to understand patterns.
Instructions
-
Analyze existing page patterns
- Read existing pages
- Identify: file structure, layout usage, data fetching pattern, state management
- Note naming conventions (PascalCase, kebab-case, etc.)
-
Create page component
- Path: according to framework convention
- Next.js App Router:
app/{{input.route}}/page.tsx - Next.js Pages:
pages/{{input.route}}.tsx - React Router:
src/pages/{{input.name}}.tsx
- Next.js App Router:
- Use layout "{{input.layout}}"
- Implement basic structure: header, content area, loading state, error state
- Path: according to framework convention
-
Create sub-components (if page is complex)
- Break into reusable components
- Path:
src/components/{{input.name}}/ - Each component: file + test
-
Setup data fetching
- Follow existing patterns (SSR, client-side, React Query, SWR, etc.)
- Create mock data for development
-
Create tests
- Render test (component mounts without error)
- Interaction tests (click, form submit, navigation)
- Data fetching tests (loading, success, error states)
-
Update navigation (if applicable)
- Add link to the new page in navbar/sidebar
Script
#!/bin/bash
# Detect framework routing
if [ -d "app" ] && [ -f "next.config.mjs" -o -f "next.config.js" -o -f "next.config.ts" ]; then
echo "Framework: Next.js App Router"
echo "Page path: app/{{input.route}}/page.tsx"
elif [ -d "pages" ] && [ -f "next.config.mjs" -o -f "next.config.js" -o -f "next.config.ts" ]; then
echo "Framework: Next.js Pages Router"
echo "Page path: pages/{{input.route}}.tsx"
elif [ -d "src/pages" ]; then
echo "Framework: React (Pages pattern)"
echo "Page path: src/pages/{{input.name}}.tsx"
fi
Validation
- Page component renders without error
- Route accessible in browser (dev server)
- Layout applied correctly
- Loading state works
- Error state works
- Tests passing
- Typecheck passing
- Navigation updated (if applicable)
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.
- 1mo ago First seen · 87 lines · 19 tokens per session scan A 4925e717ba5b
scaffold-webapp is a skill published in the GitHub repository porcupine-md/jonggrang (16 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 715 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.