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 YourTechBud/coding-harness-config --skill shaping-issuesgit clone --depth 1 https://github.com/YourTechBud/coding-harness-configWrote 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/yourtechbud/coding-harness-config/shaping-issues)<a href="https://agentmods.dev/skills/yourtechbud/coding-harness-config/shaping-issues"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/shaping-issues/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/yourtechbud/coding-harness-config/shaping-issues"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/shaping-issues.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.00033 | $0.01516 |
| Opus 5.5 | $0.00013 | $0.00606 |
| Sonnet 5.5 | $0.00007 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
shaping-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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shaping Issues
Shape bounded product milestones, called epics, and the stories supported by current understanding. Pair with the brainstorming skill for questioning, research, and shared understanding. Help the user evaluate value, alternatives, and tradeoffs; the user owns consequential decisions.
Shaping Phases
Use these phases to guide the conversation with the user, making the current phase and its purpose clear. Develop shared understanding together before advancing to decisions that depend on it.
- Problem discovery: establish the problem and its context. Use existing information and ask questions to draw out missing needs, circumstances, and assumptions the user may not have articulated.
- Discover value: explore who benefits, what product outcome would meaningfully improve the problem, and why that outcome matters. Establish the desired value before choosing features or an engineering approach.
- Converge: explore alternative ways to deliver that value and help the user choose the product approach and features to pursue.
- Sharpen: shape a coherent epic within its budget, ambitious in outcome and minimal in mechanism. Propose the smallest scope that delivers it and walk the user through what the epic will do and what it will not handle, including edge cases and guarantees whose handling would add mechanism such as extra state, protocols, retries, or schema. Give each exclusion its default behavior so the user can confirm, override, or explore it, and group items so the walkthrough stays short. Carve the agreed scope into substantial stories that deliver meaningful value and whose designs the user can comprehend as a whole.
- Harden: review the chosen epic's goal, rationale, scope and exclusions, completion condition, and supported stories. Address remaining details and make consequential uncertainty explicit, using spikes where needed; readiness may mean a clear investigation rather than a complete implementation backlog.
Sharpen and Harden may share an exchange, but give scope shaping and final review distinct attention. Revisit earlier phases when new understanding warrants it. After a spike or other new evidence, resume from established context at the phases affected by what changed.
What ships with it
1 file 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 8e554690a06f
- 1mo ago Changed 1fe1d059cc3b
- 1mo ago Changed · +4 lines d7c783987595
- 1mo ago Changed · +7 lines · -53 tokens per session fbaa6426101c
- 2mo ago First seen · 55 lines · 86 tokens per session scan A 613141c76c92
shaping-issues is a skill published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 1,516 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…