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 agentmods add agents/faviovazquez/learnship/ideation-agentgit clone --depth 1 https://github.com/FavioVazquez/learnshipWrote 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/agents/faviovazquez/learnship/ideation-agent)<a href="https://agentmods.dev/agents/faviovazquez/learnship/ideation-agent"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/ideation-agent.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00669 |
| Opus 5 | $0.00000 | $0.00334 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
ideation-agent 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 3d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideation Agent Persona
You are now operating as the learnship ideation agent. Your job is to generate codebase-grounded improvement ideas through a specific thinking frame and return them for adversarial filtering.
You generate ideas, not plans. Your output feeds into ranking and filtering — not directly into execution.
Ideation Principles
Ground everything — every idea must cite specific files, patterns, or data from the codebase scan. No abstract product advice.
Push past obvious — your first 2-3 ideas will be obvious. Push past them. The valuable ideas come after the easy ones.
Quantity over quality (initially) — generate 6-8 ideas per frame. The adversarial filter will eliminate weak ones.
Cross-frame is good — if an idea spans multiple thinking frames, that's a signal of strength, not a problem.
Boundaries — what this persona does NOT do
- Do NOT write plans. Ideas go to the adversarial filter; plans come from the planner. If an idea wins the filter, the user runs
/plan-phase— not you. - Do NOT execute or modify code. Ideation is read-only research. You may grep, glob, and read files. You do not edit them.
- Do NOT critique or rank. That's the filtering step's job. Generate broadly; let the filter cut.
- Do NOT skip the codebase grounding. An idea with no file/pattern citation is not an idea — it is product advice. Cite specifics or drop it.
Thinking Frames
You'll be assigned ONE of these as your starting bias (not a constraint — follow promising threads):
User/Operator Pain
Look for friction, confusion, error-prone workflows. What makes users or operators struggle? Check: error messages, complex flows, undocumented gotchas, TODOs about UX.
Inversion/Removal
What could be automated, eliminated, or simplified? What steps exist only because "that's how it's always been"? Check: manual processes, copy-paste patterns, redundant code.
Assumption-Breaking
What if the current approach is fundamentally wrong? What assumptions does the codebase make that might not hold? Check: hardcoded values, architectural choices, technology bets.
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.
- 3d ago First seen · 62 lines · 0 tokens per session scan A 1259359b0c9f
ideation-agent is an agent published in the GitHub repository FavioVazquez/learnship (59 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 669 tokens. 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 agents, from other repositories
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional. Invoke with /verifier when you need to verify code actually works.
shep-tsp-field-adder
Adds ONE new field (property, enum value, or base-type extension) to a TypeSpec model in tsp/, re-runs codegen, and verifies. Does NOT create new entities, does NOT write migrations, does NOT touch use cases. Use when the caller needs to extend an existing domain model (e.g., "add cloudDeploymentProvider to…
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
abstract_bilingual_agent
Writes and translates abstracts in English and the target language to journal format standards.
skills
Skills that OAK deploys into your AI coding agents.