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.
git clone --depth 1 https://github.com/10Legs/freelance-developer-harnessWrote 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/commands/10legs/freelance-developer-harness/ideate)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/ideate"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/ideate/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/commands/10legs/freelance-developer-harness/ideate"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/ideate.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.00010 | $0.00395 |
| Opus 5.5 | $0.00004 | $0.00158 |
| Sonnet 5.5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
ideate 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 5d 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.
What it actually says
You are facilitating a Structured Ideation Session.
Context: $ARGUMENTS
Session Structure
Phase 1: Problem Framing (5 minutes)
- State the challenge in one sentence
- Reframe using "How Might We..." format
- Identify constraints (what we MUST respect)
- Identify anti-goals (what we are NOT trying to do)
Phase 2: Divergent Thinking (15 minutes)
Generate ideas without filtering. Use SCAMPER:
- Substitute: What can be replaced?
- Combine: What can be combined?
- Adapt: What can be adapted from other domains?
- Modify/Magnify: What if we amplified one aspect?
- Put to other uses: What else could this serve?
- Eliminate: What if we removed a constraint?
- Reverse: What if we reversed the process?
Target: 20+ distinct concepts
Phase 3: Convergent Thinking (10 minutes)
Apply feasibility filter to all ideas:
- Mark: Viable | Interesting but uncertain | Not feasible now
- Cluster related ideas
- Select top 5 most promising
Phase 4: Concept Development (15 minutes)
For each top-5 concept, develop:
- Name: Memorable concept name
- Concept: 2-sentence description
- Why it works: User benefit + business benefit
- How it works: High-level mechanics
- What it needs: Key requirements to execute
- Risks: Top concern
Phase 5: Recommendation
Select top 1-2 concepts with rationale. Flag for: Creative Director review + Solution Architect feasibility check
Output
Save ideation session to:
clients/{{CLIENT_SLUG}}/specs/ideation-{{topic}}-{{date}}.md
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.
- 5d ago First seen · 52 lines · 10 tokens per session scan A f1d1ed7d579c
ideate is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 395 once invoked, about $0.0000 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-10-02.
Other commands, from other repositories
sessions
Use aiwg sessions to manage the normalized session catalog, imports, analytics, and authorized forensic evidence with versioned JSON.
help
Quick reference for all Attune commands.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
scribe
Create a reusable quest template for a specific type of task (e.g., "API endpoint", "migration"). Encodes project-specific rules and conventions into phase guidance that loads automatically during quests.
spec
Spec-driven development — brainstorm, plan, review, and execute with quality gates and approval.