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 submit-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/submit-task)<a href="https://agentmods.dev/skills/uhappylogic/cairn/submit-task"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/submit-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/submit-task"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/submit-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.00026 | $0.01410 |
| Opus 5.5 | $0.00010 | $0.00564 |
| Sonnet 5.5 | $0.00005 | $0.00282 |
| Haiku 4.5 | $0.00003 | $0.00141 |
Grade A, and why
submit-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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
submit-task
Turns a single, already-clear issue into a brief-level task section in the current
milestone's TASKS_TODO.md. This skill is the user-facing entry point
(/submit-task) and the handoff target for /discuss-new-task.
It owns the triage and positioning that need the whole task list in view — checking for
duplicates and deciding where the task belongs — and then it authors and inserts the task
inline, in this conversation. If the issue is still vague or might be several tasks,
use /discuss-new-task first.
Invocation
/submit-task <issue description>
<issue description> is a free-form description of a problem or gap discovered during
development, specific enough that the affected system, desired behavior, and how to verify
it are clear.
Workflow
0. Find the current milestone
Follow {{PLUGIN_ROOT}}/shared/get-current-milestone.md to resolve <MILESTONE_DIR>. Never use a hardcoded task-list path.
1. Read context for triage
Read in parallel:
<MILESTONE_DIR>/requirements.md— to confirm the issue fits the milestone's scope.<MILESTONE_DIR>/TASKS_TODO.md— existing pending tasks, for duplicate-detection and positioning.<MILESTONE_DIR>/TASKS_DONE.md— completed work, to catch issues already addressed.
2. Triage
- Duplicate? If an existing pending task or a completed task already covers this issue, stop and tell the user which task covers it. Do not add a duplicate.
- In scope? If the issue clearly belongs to a different milestone or is really an open design decision, say so and point to the better tool (
/discuss-open-question) instead of queuing it.
3. Decide the position
You hold the whole task list, so you decide where the task goes:
- If the task is a prerequisite for an existing task, position it before that task:
before: <Task Title>. - If it depends on an existing task, position it after that task:
after: <Task Title>. - Otherwise,
append.
4. Author the task section inline
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.
- 3d ago Changed · +15 lines 5d98300843f3
- 1mo ago Changed d3727470a6eb
- 1mo ago Changed · -1 lines db6695157462
- 1mo ago Changed · -19 lines · -48 tokens per session d8b6e9d9a6fe
- 1mo ago Changed · +23 lines · +1 tokens per session 4f6385768e35
- 1mo ago First seen · 104 lines · 73 tokens per session scan A 59f840254d0e
submit-task is a skill published in the GitHub repository uHappyLogic/cairn (3 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,410 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
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…
hermit-scribe
File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.