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 002-agents-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/002-agents-inventory)<a href="https://agentmods.dev/skills/jabrena/plinth/002-agents-inventory"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/002-agents-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/002-agents-inventory"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/002-agents-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.00090 | $0.00551 |
| Opus 5.5 | $0.00036 | $0.00220 |
| Sonnet 5.5 | $0.00018 | $0.00110 |
| Haiku 4.5 | $0.00009 | $0.00055 |
Grade A, and why
002-agents-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 27d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Checklist with embedded agents inventory for Java
Create a comprehensive checklist document for embedded agents inventory by following the embedded template exactly.
What is covered in this Skill?
- Exact-template checklist generation
- Output file creation as
INVENTORY-AGENTS-JAVA.md - Strict adherence to listed sections and content
Constraints
Follow the template exactly without adding or removing sections, rows, or details.
- DO NOT create additional rows beyond what the template defines
- DO NOT add agent entries not explicitly listed in the template
- ONLY use exact wording and structure from the embedded template
- 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 embedded agents inventory checklist
- Generate INVENTORY-AGENTS-JAVA.md
- Use @002-agents-inventory
- Inventory embedded Java agent definitions
- List generated agent roles for Java development
Workflow
- Read the embedded template
Read references/002-agents-inventory.md before generating output and use it as the authoritative template.
Step constraints:
- Do not use cached or partial template content
- Preserve exact table rows, headings, and structure from the reference
- Generate inventory document
Create INVENTORY-AGENTS-JAVA.md in the project root using the exact wording and ordering from the reference template.
- Validate template fidelity
Confirm no extra agent rows were introduced and all required reference sections are present in the generated file.
Reference
For detailed guidance, examples, and constraints, see references/002-agents-inventory.md.
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.
- 27d ago Changed 2d107d0ef0eb
- 1mo ago First seen · 59 lines · 90 tokens per session scan A 42e44dbdfe40
002-agents-inventory is a skill published in the GitHub repository jabrena/plinth (455 stars, last pushed 3d ago), licensed Apache-2.0. It adds 90 tokens to every session and 551 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.