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/destrayon/connapse/next-tasknpx skills add Destrayon/Connapse --skill next-taskgit clone --depth 1 https://github.com/Destrayon/ConnapseWhat 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.00066 | $0.01209 |
| Opus 5 | $0.00033 | $0.00605 |
| Sonnet 5 | $0.00013 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
next-task 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Task
Analyze open GitHub issues and recommend the best task to start working on right now.
Step 1: Gather Context
Run these in parallel to understand the current state:
Open issues and board state
gh issue list --repo Destrayon/Connapse --state open --json number,title,labels,milestone,assignees,createdAt,updatedAt --limit 100
Current branch and working state
git status --short
git branch --show-current
Recent activity (what was just worked on)
gh pr list --repo Destrayon/Connapse --state merged --json number,title,mergedAt,labels --limit 5
Check decisions.md and issues.md for blockers or context
Read .claude/state/decisions.md and .claude/state/issues.md for any known blockers, dependencies, or recent decisions that affect prioritization.
Step 2: Score and Rank
Evaluate each open issue against these criteria, in order of importance:
Priority Weight (highest impact)
| Priority | Score |
|---|---|
| P0-Critical | 100 |
| P1-High | 70 |
| P2-Medium | 40 |
| P3-Low | 10 |
| No priority set | 20 |
Milestone Urgency
Issues in the nearest milestone score higher. The reasoning: shipping a complete milestone is more valuable than scattering work across multiple milestones.
| Milestone | Score |
|---|---|
| Current (nearest due date or lowest version) | +30 |
| Next | +15 |
| Future | +5 |
| No milestone | +0 |
Dependency Readiness
An issue that has no blockers and no unmerged dependencies should score higher than one waiting on other work. Check:
- Does the issue body reference other issues it depends on? Are those closed?
- Is the issue marked
blocked? - Would this issue unblock other issues? (check if other issues reference this one)
| Status | Score |
|---|---|
| Unblocks other issues | +25 |
| No dependencies, ready to start | +15 |
| Dependencies met (referenced issues are closed) | +10 |
| Has open dependencies | -30 |
Labeled blocked |
-50 |
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 · 135 lines · 66 tokens per session scan A aabf12fd3e62
next-task is a skill published in the GitHub repository Destrayon/Connapse (16 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 1,209 once invoked, about $0.0003 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
collattice
Operate a Collattice kanban board through its Model Context Protocol (MCP) endpoint — connecting, authentication, the board model, identifier rules (board-level reads need a board GUID, not a slug), the Markdown a board renders, and the full tool reference: reading and creating cards, moving and reordering lanes…
triage-tasks
Use when you want to review and batch-update open vault task statuses for the current project or across all projects.
tackle-task
Use when starting work on a specific vault task, when a task title or path is mentioned, or when coming from triage output.
add-task
Use when you want to quickly capture a new task in the vault from a title, with optional priority and due date.
kioku-project-workflow
Use when a user asks to start, resume, plan, implement, review, debug, or document substantial work for a project managed through the Kioku MCP server.
dotnet-mcaf-agile-delivery
Apply MCAF agile-delivery guidance for backlog quality, roles, ceremonies, and engineering feedback. Use when defining how the team plans, tracks work, and turns feedback into durable improvements.