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/commands/jabrena/plinth/explore-design)<a href="https://agentmods.dev/commands/jabrena/plinth/explore-design"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/explore-design/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/commands/jabrena/plinth/explore-design"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/explore-design.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.00015 | $0.00936 |
| Opus 5.5 | $0.00006 | $0.00374 |
| Sonnet 5.5 | $0.00003 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
explore-design 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 2mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
explore-design
Improve and refine the technical approach for an issue or OpenSpec change after initial specification—with alternatives, trade-offs, compatibility review, rollout controls, and verification strategy—before implementation.
Usage
/explore-design <issue|openspec-change>
Accepted Inputs
- Issue or user story
- OpenSpec change with unresolved technical approaches or design gaps
- Existing architecture context and constraints
- Relevant requirements, ADRs, or technical notes linked to the issue or change
Owning Agent
@plinth-architect
Associated Skills
051-design-two-steps-methodsfor every refinement so preparatory work, behavior change, and verification remain explicitly sequenced052-design-hamburger-methodwhen the scope is broad enough to need smallest-useful vertical slices053-design-simple-ruleswhen alternatives need ordered design tradeoff evaluation before finalizing the direction054-design-tddwhen testing-related requirements need test-first sequencing and verification-driven refinement055-design-parallel-changewhen database migration requirements need expand, migrate, contract sequencing056-design-avoid-breaking-changeswhen compatibility surfaces may change during refinement057-design-feature-toggleswhen rollout, rollback, compatibility windows, or temporary behavior controls affect the design direction059-design-atddas the final alignment gate when an OpenSpec change provides a proposal, specification scenarios, and a task checklist121-java-object-oriented-design, then122-java-type-design, then123-java-design-patternswhen Java responsibilities, type boundaries, or collaboration decisions affect the refined approach130-java-testing-strategieswhen testing strategy, boundary coverage, flakiness, or verification quality affect the refined approach
Workflow position
Runs after /create-spec, not as the first mission in the workflow.
Workflow
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.
- 2mo ago First seen · 81 lines · 15 tokens per session scan A d4bbd399bc76
explore-design is a command published in the GitHub repository jabrena/plinth (461 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 936 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.
explore-design compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| explore-designjabrena/plinth | Command | 461 | yesterday | Apache-2.0 | A | 15 | Claude Code, Cursor |
| earningslongbridge/skills | Command | 71 | 4d ago | MIT | A | 23 | Claude Code |
| skill-evalcitedy/skills | Command | 2 | 5mo ago | MIT | A | 35 | Claude Code |
| reviewKhaiTrang1995/claude-code-structure | Command | 2 | 6mo ago | MIT | A | 0 | Claude Code |
| startjperrello/C0BALT_CUT | Command | 3 | 3mo ago | none | A | 62 | Claude Code |
| resolve-review.bodysergeyklay/.agents | Command | 6 | 3d ago | Apache-2.0 | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |