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 skills/alecs5am/ralphy/dev-tasksnpx skills add alecs5am/ralphy --skill dev-tasksgit clone --depth 1 https://github.com/alecs5am/ralphyWhat 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.00278 | $0.02199 |
| Opus 5 | $0.00139 | $0.01099 |
| Sonnet 5 | $0.00056 | $0.00440 |
| Haiku 4.5 | $0.00028 | $0.00220 |
Grade A, and why
dev-tasks 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 2d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev-tasks — the capture-inbox manager for Ralphy dev work
This is a maintainer skill. It does not touch .ralphy/workspaces/<ws>/projects/ or call media models. It curates the notes/ capture inbox that tracks Ralphy's own development. notes/ is the only tracker — there is no separate roadmap board.
- Inbox —
notes/ideas/,notes/issues/,notes/decisions/. Free-form, monotonic-numbered (NNN-slug.md). The landing zone for any dev thought. notes/issues/is the live backlog, status-by-folder: flat top level = active,done/= resolved/landed,deprecated/= superseded/won't-do.
The contract lives in notes/README.md. Read it before your first capture or move in a session — this skill is the operator, that file is the law.
Division of labor with dev-issues / dev-loop
- This skill (
dev-tasks) ownsideas/+decisions/capture and the cross-inbox collision check. dev-issuesowns thenotes/issues/backlog: decomposing a brain-dump into well-shaped issue files, shaping them, filing/updating them. Read.agents/skills/dev-issues/SKILL.mdbefore doing any non-trivial issue work — don't duplicate its job here.dev-loopowns issue execution (pick → implement → move todone/).
When a captured idea matures into something actionable, promote it into a notes/issues/ item (per notes/README.md) and hand the shaping/execution to dev-issues / dev-loop.
Trigger
Hard triggers (always act):
- User types
/dev-tasks. - "log this / file this / capture this" + an idea, bug, or design thought about Ralphy itself.
- "record this decision" / "promote this note".
- "what's in the inbox" / "what's open".
- "is there already a note/idea for X" → run the collision check and report.
ALSO FIRE (proactively, offer — don't auto-execute)
- The user surfaces a design idea mid-dev-session and moves on without filing it → offer to capture it before it's lost.
- A note in
notes/ideas/has clearly matured (concrete acceptance criteria, no open questions) → offer to promote it into anotes/issues/item.
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.
- 2d ago First seen · 113 lines · 278 tokens per session scan A 76c85476cc00
dev-tasks is a skill published in the GitHub repository alecs5am/ralphy (128 stars, last pushed 7d ago), licensed Apache-2.0. It adds 278 tokens to every session and 2,199 once invoked, about $0.0014 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
gini-bug-report
File a locally-captured, already-redacted Gini crash report as a GitHub issue, with the user's consent. Reads the pending crash queue and delegates the actual filing to the github-issues skill.
github-issues
Create, search, triage, label, assign, comment on, and close GitHub issues using the gh CLI, with a curl REST fallback.
linear
Read and write Linear issues, comments, projects, cycles, users, documents, initiatives, milestones, and more via the Linear MCP server. Attach chat-uploaded screenshots to issues.
morning
Use when performing daily status check-ins, PR reviews, and morning workflow routines.
copilotkit-contribute
Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.
gget
Fast CLI/Python queries to 20+ bioinformatics databases. Use for quick lookups: gene info, BLAST searches, AlphaFold structures, enrichment analysis. Best for interactive exploration, simple queries. For batch processing or advanced BLAST use biopython; for multi-database Python workflows use bioservices.