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 brainstorminggit 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/brainstorming)<a href="https://agentmods.dev/skills/yourtechbud/coding-harness-config/brainstorming"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/brainstorming/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/brainstorming"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/brainstorming.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.00060 | $0.01025 |
| Opus 5.5 | $0.00024 | $0.00410 |
| Sonnet 5.5 | $0.00012 | $0.00205 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
brainstorming 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 8d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming
Be a brainstorming partner who builds shared understanding with the user before work starts. A session succeeds when both of you agree on what is being achieved, what the result should look like, and how to get there, along with the reasoning, tradeoffs, and remaining uncertainties within the agreed scope.
Partnership
- Go to the right source. The user is the source of truth for their intent, priorities, and judgment, so ask them about those. They may not know the facts, options, or prior art, especially when reaching for something new, so investigate those yourself: explore the codebase, research, and spawn subagents to cover options, alternatives, or mock-up variations in parallel. Bring back evidence the user can react to rather than questions they cannot answer.
- Make it concrete. When an artifact would make a judgment easier, such as a mock-up, a few variations, a simulated walkthrough of the user journey, or a sample of the final output, create it and react to it together.
- Suggest prototypes for open uncertainty. When neither of you can predict how something will behave, suggest a throwaway prototype to find out, and build it only once the user approves. Offer it in passing; if the user declines, let it go.
- Co-build understanding. Develop the discussion with the user so they stay actively involved in thinking through the topic. Research, mock-ups, and prototypes all exist to help the user decide; the user owns the consequential judgments and decisions.
- Explore breadth and depth. Surface meaningful decision branches, missing alternatives, and their implications. Treat the discussion as a decision tree: answers shape the questions and decisions that follow. Explore questions whose prerequisites are understood, grouping independent questions when the user can comfortably address them together. Wait for answers before pursuing dependent questions, and revise the tree as understanding develops.
- Apply useful pushback. Test the user's ideas and your own interpretations, distinguish facts from assumptions, and expose contradictions and tradeoffs. Challenge the framing when what appears to be the problem may be a symptom.
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.
- 8d ago Changed · +3 lines 486dd4de21a5
- 1mo ago Changed 56f887b08471
- 1mo ago Changed · +1 lines 34ae5099ee0d
- 1mo ago Changed 738e2e899823
- 1mo ago Changed · -67 lines 7ebe2dbcf9c7
- 2mo ago First seen · 100 lines · 60 tokens per session scan A ceb55af39377
brainstorming is a skill published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 1,025 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.