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 componentgit 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/component)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/component"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/component/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/component"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/component.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.00016 | $0.00539 |
| Opus 5.5 | $0.00006 | $0.00216 |
| Sonnet 5.5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
component 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.
What it actually says
Context
Project {{project_name}} uses {{stack}}. Create component "{{input.name}}" of type {{input.type}}.
Read AGENTS.md for component conventions. Read existing components to understand patterns (styling, state, testing).
Instructions
-
Analyze existing component patterns
- Check component directory structure
- Identify: styling approach (CSS Modules, Tailwind, styled-components)
- Identify: state management (useState, Zustand, Redux, etc.)
- Identify: testing pattern (render tests, user-event, MSW)
-
Create component file
- Path: according to project convention
src/components/{{input.name}}/{{input.name}}.tsx- or
src/components/{{input.name}}.tsx
- Props interface with TypeScript
- Implement component according to type:
ui: presentational, props-drivenform: form state, validation, submit handlerdata-display: data fetching, loading/error stateslayout: children, responsive designpage: composition of other components
- Path: according to project convention
-
Create barrel export (if the project uses this pattern)
src/components/{{input.name}}/index.ts
-
Create test file
- Path: co-located or in test directory
- Tests:
- Renders without crashing
- Renders with different props
- User interactions (click, type, etc)
- Edge cases (empty data, long text, etc)
-
Create story (if the project uses Storybook)
- Path: co-located
{{input.name}}.stories.tsx - Default story + variants
- Path: co-located
Validation
- Component renders without error
- TypeScript types correct (no any)
- Tests passing
- Styling consistent with existing components
- Accessible (semantic HTML, aria labels if needed)
- Responsive (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 · 71 lines · 16 tokens per session scan A 72611b2999c0
component is a skill published in the GitHub repository porcupine-md/jonggrang (16 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 539 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.