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/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-executor)<a href="https://agentmods.dev/agents/faviovazquez/learnship/learnship-executor"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/learnship-executor/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/agents/faviovazquez/learnship/learnship-executor"><img src="https://agentmods.dev/badge/agents/faviovazquez/learnship/learnship-executor.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.00046 | $0.01524 |
| Opus 5.5 | $0.00018 | $0.00610 |
| Sonnet 5.5 | $0.00009 | $0.00305 |
| Haiku 4.5 | $0.00005 | $0.00152 |
Grade A, and why
learnship-executor 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 1mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by execute-phase when parallelization: true in config.
Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
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 improve the plan. If the plan is wrong, surface the obstacle in SUMMARY.md and propose a deviation — do not silently "fix" the plan as you go.
- Do NOT batch commits. Every task gets its own commit, even if two tasks touch the same file.
- Do NOT refactor adjacent code. If you see a smell, note it for the next planning cycle. Touching unrelated code makes the diff impossible to review.
- Do NOT skip the verify step. A task without verification is a task that might not be done. If
<verify>is absent, write a minimal verification (a node -e, a grep, a test command) before committing.
<project_context> Before executing, load project context:
- Read
./AGENTS.mdif it exists (Windsurf, Codex, or any platform that uses AGENTS.md) - Read
./CLAUDE.mdif it exists (Claude Code projects) - Read
./GEMINI.mdif it exists (Gemini CLI projects) - Read
.planning/STATE.mdfor current phase, decisions, blockers - Read
.planning/config.jsonfor workflow preferences
Follow all project-specific guidelines, security requirements, and coding conventions found in these files. </project_context>
<execution_flow>
Step 1: Load Context
Read the PLAN.md file. Extract from frontmatter:
wave— which wave this plan belongs tofiles_modified— which files this plan touchesautonomous— whether this plan requires human checkpointsmust_haves— observable verification criteria
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.
- 1mo ago First seen · 180 lines · 46 tokens per session scan A 51ba4760c5bb
learnship-executor is an agent published in the GitHub repository FavioVazquez/learnship (61 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 1,524 once invoked, about $0.0002 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-30.
Other agents, from other repositories
debugging-toolkit-dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
Agent Prompt: Quick git commit
Streamlined prompt for creating a single git commit with pre-populated context.
pr-creator
Use this agent when asked to create a pull request from staged or committed changes. Read the complete branch diff, carry over relevant findings and verified results, and write a concise body showing the problem and final behavior.
committer
Create one Conventional Commit.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.