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 SymbolicLight-AGI/contractual-skill --skill brainstorminggit clone --depth 1 https://github.com/SymbolicLight-AGI/contractual-skillWrote 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/symboliclight-agi/contractual-skill/brainstorming)<a href="https://agentmods.dev/skills/symboliclight-agi/contractual-skill/brainstorming"><img src="https://agentmods.dev/badge/skills/symboliclight-agi/contractual-skill/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/symboliclight-agi/contractual-skill/brainstorming"><img src="https://agentmods.dev/badge/skills/symboliclight-agi/contractual-skill/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.00035 | $0.01044 |
| Opus 5 | $0.00017 | $0.00522 |
| Sonnet 5 | $0.00007 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
brainstorming-contractual 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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs Contract
When To Use
Use this Skill before implementation when the user has a raw idea, design question, architectural direction, behavior change, or feature concept that needs clarification.
Do not use this Skill as an implementation mode. If the user asks to code, modify behavior, create files, deploy, or make irreversible changes while this Skill is active, stop and ask for an explicit transition to an implementation workflow.
Goal
Turn vague ideas into clear, validated designs and specifications. The useful outcome is shared understanding, explicit assumptions, documented decisions, risks, and an implementation handoff only after the design is accepted.
Audience
- Product or business owners clarifying desired behavior.
- Engineers exploring architecture, components, data flow, edge cases, or test strategy.
- Reviewers who need a decision log and assumptions before implementation.
Inputs
- Required: the idea, feature, behavior, architecture question, or problem to explore.
- Optional: current files, documentation, plans, prior decisions, constraints, success criteria, non-goals, and project standards.
- Privacy: do not repeat credentials, secrets, customer data, or private production details unless they are necessary and safely redacted.
If key context is missing, continue only by marking assumptions and asking one focused question at a time.
Context
Review available project state before designing when project context is provided. Distinguish what already exists from what is proposed. Treat unconfirmed constraints as assumptions.
Do not speculate about repository files, architecture, or prior decisions without evidence from user-provided material or read-only inspection.
Workflow
- Understand current context before proposing solutions.
- Ask one question per message, preferring multiple-choice questions when useful.
- Clarify purpose, target users, constraints, success criteria, and explicit non-goals.
- Clarify or propose assumptions for performance, scale, security, privacy, reliability, maintenance, and ownership.
- Create an understanding summary with assumptions and open questions.
- Do not proceed to design until the user confirms the understanding.
- Explore 2-3 viable approaches and lead with a recommended option.
- Compare tradeoffs in complexity, extensibility, risk, and maintenance.
- Present the design incrementally and validate each section.
- Maintain a decision log with decisions, alternatives, and rationale.
- After validation, prepare documentation or an implementation handoff if explicitly requested.
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.
- 9d ago First seen · 138 lines · 35 tokens per session scan A 27cccd90bd22
brainstorming-contractual is a skill published in the GitHub repository SymbolicLight-AGI/contractual-skill (21 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,044 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…