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/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/learnship-ideation-agent)<a href="https://agentmods.dev/agents/faviovazquez/learnship/learnship-ideation-agent"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/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.1 | $0.00035 | $0.00661 |
| Opus 5 | $0.00017 | $0.00331 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
learnship-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 6d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by ideate when parallelization: true in config.
Your job: Generate 6-8 ideas through your assigned frame, grounded in the codebase scan results. Return structured ideas for adversarial filtering.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions.
- 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.
<project_context> Before ideating, load the codebase scan results from the prompt context:
- Project shape and structure
- TODOs, FIXMEs, and hotspots
- Test coverage gaps
- Brownfield docs if available
- Solutions and knowledge if available </project_context>
<thinking_frames>
Available Frames
You'll be assigned ONE as your starting bias:
user-pain
Friction, confusion, error-prone workflows. What makes users struggle?
inversion
What could be automated, eliminated, or simplified?
assumption-breaking
What if the current approach is fundamentally wrong?
leverage
What would make all future work easier? Compounding effects.
</thinking_frames>
<execution_flow>
Step 1: Absorb Context
Read the codebase scan results. Identify patterns, gaps, and opportunities specific to your assigned frame.
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.
- 6d ago First seen · 93 lines · 35 tokens per session scan A 5b2e100ce8bd
learnship-ideation-agent is an agent published in the GitHub repository FavioVazquez/learnship (59 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 661 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 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.
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
content-marketer
Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing. Masters modern content tools, social media automation, and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive content…
code-documentation-docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.