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 setup-brainstorming-artifactsgit 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/setup-brainstorming-artifacts)<a href="https://agentmods.dev/skills/yourtechbud/coding-harness-config/setup-brainstorming-artifacts"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/setup-brainstorming-artifacts/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/setup-brainstorming-artifacts"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/setup-brainstorming-artifacts.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.00022 | $0.01072 |
| Opus 5.5 | $0.00009 | $0.00429 |
| Sonnet 5.5 | $0.00004 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
setup-brainstorming-artifacts 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up or revise a brainstorming artifact workspace for this repo.
Do not treat this as a setup wizard. Treat it as a guided discovery process that helps the user figure out what kind of artifact workspace would meaningfully reduce cognitive load for their brainstorming process.
<operating_model>
- Start with lightweight, read-only repo discovery: check whether
.isagi/brainstorming-workspaceexists, inspect any existing guidance, and understand repo tooling only enough to avoid bad setup assumptions. - Use repo context as background, not as the main frame of the first conversation.
- Move through the work in gated stages. Internally, use stages to avoid collapsing discovery, onboarding, option discussion, and implementation into one turn. Externally, use natural language unless labels help clarity.
- After read-only discovery, do not move to a new stage without explicit user consent.
- Do not create or modify files until the user has explicitly confirmed the desired artifact experience, the principles to encode, the setup direction, and permission to implement.
- If the user asks to skip questions and "just set it up," keep the discovery lightweight, but still establish the minimum shared understanding needed before implementation. </operating_model>
<seed_principles> Use these as internal lenses during discovery and guidance creation. Do not present them as a mandatory checklist, and do not preserve rejected principles in the final workspace guidance.
- Reduce cognitive burden; the workspace should make long brainstorming easier to stay inside.
- Chat conducts; artifacts carry substantial reasoning.
- Questions should live with relevant branch context, not as detached chat lists.
- Active decision branches should usually be the main unit.
- Branches need predictable high-level anatomy, but their bodies should stay freeform; do not hardcode a universal branch body template.
- Real pushback should be visible when present.
- Artifacts should develop suggestions, tradeoffs, and options, not only questions.
- Visual form should compress thought, not decorate it.
- Minimal, quiet UI usually beats design-heavy presentation.
- Prefer linear, predictable reading flows over bento grids or dashboard-like layouts.
- Navigation should make the workspace easy to re-enter.
- Anti-staleness should not become amnesia; preserve important cumulative context.
- Implementation plans should be created only when explicitly requested. </seed_principles>
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 · 72 lines · 22 tokens per session scan A 524081174543
setup-brainstorming-artifacts is a skill published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 1,072 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
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.