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 agentmods add skills/dryvist/claude-code-plugins/shape-issuesnpx skills add dryvist/claude-code-plugins --skill shape-issuesgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWhat 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 | $0.00016 | $0.00472 |
| Opus 5 | $0.00008 | $0.00236 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
shape-issues 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 yesterday.
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
Shape Issues
Iterative issue exploration and shaping process that transforms rough ideas into well-defined, time-boxed GitHub Issues using Shape Up methodology and continuous discovery principles.
Attribution: Based on work by roksechs
Phases
- Problem Exploration: Examine raw ideas, map pain points, assess timebox
- Solution Sketching: Brainstorm approaches, set scope boundaries, identify risks
- Issue Formation: Problem statement, timebox, solution sketch, rabbit holes
- Betting Table: Prioritize by timebox, balance portfolio, set circuit breakers
- Issue Crafting: Create GitHub Issues with size labels, add
ready-for-devlabel for developer pickup
Sizing
| Label | Duration |
|---|---|
size:xs |
< 1 day |
size:s |
1-3 days |
size:m |
3-5 days |
size:l |
1-2 weeks |
size:xl |
2+ weeks |
Workflow
- Gather context:
gh issue list,gh pr list - Explore problem: user complaints, workflow friction, timebox check
- Sketch solutions: 2-3 approaches, scope boundaries, rabbit holes
- Set timebox: spike vs small batch vs big batch
- Create issue:
gh issue createwith template, addready-for-devlabel
Issue Template
Key sections: Problem (raw idea, pain, size), Solution Sketch (concept, out of scope), Rabbit Holes (complexity traps), Done Looks Like (acceptance criteria).
Usage
/shape-issues
Workflow: /shape-issues -> implementation -> /ship
Related Skills
- pr-standards (git-standards) — PR authoring and review standards applied after issues are implemented
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.
- yesterday First seen · 55 lines · 16 tokens per session scan A ca836c9b6f4b
shape-issues is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…