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 jabrena/plinth --skill 003-skills-inventorygit clone --depth 1 https://github.com/jabrena/plinthWrote 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/jabrena/plinth/003-skills-inventory)<a href="https://agentmods.dev/skills/jabrena/plinth/003-skills-inventory"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/003-skills-inventory/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/jabrena/plinth/003-skills-inventory"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/003-skills-inventory.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.00088 | $0.00676 |
| Opus 5.5 | $0.00035 | $0.00270 |
| Sonnet 5.5 | $0.00018 | $0.00135 |
| Haiku 4.5 | $0.00009 | $0.00068 |
Grade A, and why
003-skills-inventory 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Checklist with all Java steps to use with system prompts for Java
Create a comprehensive step-by-step checklist document for Java system prompts by following the embedded section template and deriving rows from plinth-skills-generator/src/main/resources/skills.xml.
What is covered in this Skill?
- Inventory-driven checklist generation
- Output file creation as
INVENTORY-SKILLS-JAVA.md - Strict coverage of every effective skill id declared in
skills.xml
Constraints
Follow the template sections exactly and use skills.xml as the single source of truth for skill rows.
- DO NOT create additional sections beyond what the template defines
- DO NOT add skill rows absent from
skills.xml - DO NOT omit any skill declared in
skills.xml - ONLY use the
skillIdattribute as the generated skill id when it exists - ONLY use the single
reference-list/referencevalue as the generated skill id whenskillIdis absent - EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
- EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
- EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off
When to use this skill
- Create Java system prompts checklist
- Generate INVENTORY-SKILLS-JAVA.md
- Use @003-skills-inventory
- Inventory Java cursor rule skills
- List available Java system prompt skills
Workflow
- Read the template and inventory source
Read references/003-skills-inventory.md and plinth-skills-generator/src/main/resources/skills.xml before generating output.
Step constraints:
- Do not use cached or remembered template content
- Preserve exact section structure from the reference
- Use
skillIdwhen present; otherwise use the single reference name
What ships with it
2 files 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.
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 Changed d1d799ebc787
- 1mo ago First seen · 62 lines · 88 tokens per session scan A 556a72b05fe9
003-skills-inventory is a skill published in the GitHub repository jabrena/plinth (456 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 676 once invoked, about $0.0004 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
flexcel-net
Use when writing C# / VB.NET / F# code that reads, writes, manipulates, or exports Excel (.xlsx / .xls) files, generates PDF or HTML from Excel, or produces data-driven reports with FlexCel Studio for .NET (TMS Software). Triggers include Excel/xlsx from C#, XlsFile, FlexCelReport, FlexCelPdfExport, FlexCelHtmlExport…
architect
Design the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
phx-document
Use when asked to document Elixir code: add or fill in @moduledoc and @doc for modules and functions. Documents tested code only; may add a README section or ADR. Not for docs lookup or audits.
jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries). Use when user has JPA performance issues, LazyInitializationException, or asks about entity relationships and fetching strategies.
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.