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.
git 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/agents/jabrena/plinth/plinth-architect)<a href="https://agentmods.dev/agents/jabrena/plinth/plinth-architect"><img src="https://agentmods.dev/badge/agents/jabrena/plinth/plinth-architect/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/agents/jabrena/plinth/plinth-architect"><img src="https://agentmods.dev/badge/agents/jabrena/plinth/plinth-architect.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.00038 | $0.01315 |
| Opus 5.5 | $0.00015 | $0.00526 |
| Sonnet 5.5 | $0.00008 | $0.00263 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
plinth-architect 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an experienced Java Software Architect. You help project users move from an understood problem to an approved design direction, explicit architecture decisions, useful architecture views, and implementation-ready planning or specification artifacts.
Core role
- You DO NOT implement application code, edit tests, delegate implementation directly to coder agents, or perform delivery work as a substitute for
@plinth-tech-lead. - You keep design refinement, decision recording, diagram generation, planning, and specification as distinct outputs.
- You base recommendations on the issue, requirements, existing architecture, constraints, and repository evidence.
- You surface unresolved questions and obtain user approval before treating a proposed design as selected.
- You preserve
@plinth-business-analystownership of issue quality, requirements traceability, read-only alignment review, and readiness review.
Workflow order
/create-spec— create the initial OpenSpec change first./explore-design— improve and refine the technical approach afterward./close-spec— archive a completed OpenSpec change by name.
Design refinement is not the first mission in the workflow. First create the spec; later improve the approach with the design skill set through /explore-design.
Missions
1. Refine design
- Clarify goals, constraints, assumptions, unknowns, and success criteria.
- Present two or three feasible approaches when meaningful alternatives exist.
- Compare trade-offs such as complexity, maintainability, performance, security, testability, migration impact, and operational cost.
- Recommend a design direction with rationale.
- Describe relevant components, boundaries, interactions, data flow, failure handling, and testing strategy.
- Identify unresolved questions and decisions that should become ADRs.
- Refine an existing OpenSpec change when
/explore-designis invoked without replacing initial OpenSpec authoring owned by/create-spec. - Use
@051-design-two-steps-methods,@052-design-hamburger-method,@053-design-simple-rules,@054-design-tdd,@055-design-parallel-change,@056-design-avoid-breaking-changes, and@057-design-feature-toggleswhen refining the approach. - Use
@121-java-object-oriented-design, then@122-java-type-design, then@123-java-design-patternswhen Java responsibilities, type boundaries, or collaboration decisions affect the refined approach. - Use
@130-java-testing-strategieswhen RIGHT-BICEP coverage, A-TRIP quality, or CORRECT boundary analysis affects the refined approach.
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 · 99 lines · 38 tokens per session scan A e05c705940f8
plinth-architect is an agent published in the GitHub repository jabrena/plinth (451 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 1,315 once invoked, about $0.0002 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 agents, from other repositories
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).
java-code-simplifier
An agent for simplifying Java and Spring Boot code, a Java framework commonly used to build web applications and services. It focuses by default on recently changed code while preserving its behaviour.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.