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 skills add uHappyLogic/cairn --skill discuss-new-taskgit clone --depth 1 https://github.com/uHappyLogic/cairnWrote 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/skills/uhappylogic/cairn/discuss-new-task)<a href="https://agentmods.dev/skills/uhappylogic/cairn/discuss-new-task"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/discuss-new-task/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/skills/uhappylogic/cairn/discuss-new-task"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/discuss-new-task.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.00033 | $0.01700 |
| Opus 5.5 | $0.00013 | $0.00680 |
| Sonnet 5.5 | $0.00007 | $0.00340 |
| Haiku 4.5 | $0.00003 | $0.00170 |
Grade A, and why
discuss-new-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 today.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
discuss-new-task
Facilitates a short, focused conversation that turns a half-formed issue — the kind that surfaces mid-flight — into a description concrete enough to become a task. This skill is the conversational front-end for /submit-task: it clarifies just enough, then proposes the handoff. It never creates or edits any files, including the task list — producing the task(s) is submit-task's job.
Most issues are a single task. But some are a bigger chunk of work that only makes sense as several tasks — the user may flag this up front ("this might be a few entries"), or it may become apparent mid-discussion that one "issue" is really two or three independent pieces. When that happens, this skill helps draw the boundaries and produces an ordered set of task-sized descriptions, then hands each off in turn.
The bar to clear is conceptual clarity, not full design detail. For each task that comes out of the discussion, three things must be unambiguous:
- Which system the issue touches (a file, component, section, or requirement).
- What the desired behavior is — what should be true after the fix that isn't true now.
- Roughly how you'd verify it — what you'd look at to confirm it's done.
When the work splits into several tasks, one more thing must be clear: where the boundaries are — each piece should be independently completable, and their order (what depends on what) should be evident.
Once those are clear, submit-task takes over — keep what you produce high-level. Don't push the conversation, or the descriptions you write, past conceptual clarity.
Usage
/discuss-new-task [--milestone <milestone_id>] <issue description>
--milestone <milestone_id>: optional and leading; names the milestone by its exact directory name undermilestones/, e.g.milestone_12_user-guide, in place of the current-milestone pointer.<issue description>: a free-form, possibly rough description of a problem, gap, or idea surfaced mid-flight. May be a single issue or a larger "we need to create X" that spans several pieces.
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.
- today Changed · +1 lines f7e9e156cdca
- 24d ago Changed 705d05734375
- 1mo ago Changed 87f9ce7f0b24
- 1mo ago Changed 0265471630bc
- 1mo ago Changed · -10 lines · -137 tokens per session f7f7a36689d6
- 1mo ago First seen · 130 lines · 170 tokens per session scan A a6986d8ee2e4
discuss-new-task is a skill published in the GitHub repository uHappyLogic/cairn (3 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,700 once invoked, about $0.0001 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-31.
Other skills, from other repositories
scout-ask
Use when the working directory is a Scout vault (it has knowledge-base/ and action-items/) and the user asks about the state of a project, initiative, person, decision, meeting or open thread ("where are we on X", "what's going on with Y", "who is Z", "what's on my plate"), or what Scout knows about a topic. Do not…
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
scout-briefing
Launch a Scout morning briefing session as a background process. Auto-detects mode (morning briefing, consolidation, or weekend briefing) from the current time and day.
scout-dream
Launch a Scout dreaming session as a background process. Processes feedback, does KB deep work, and works on wishlist items.
debt-ops-review
Audit the tech-debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or check the debt registry. Stale entries drop with "drop A,B,C".
tackle-issue
Start-of-work triage in this monorepo. Trigger on: a GitHub issue number ("tackle issue 99", "work on #42", bare #N), pasted proposal/spec text ("investigate this", "pressure-test this", "scope this"), or picker phrasing ("tackle the next issue", "what should I work on"). Read-only investigation that tries to falsify…