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/loncadev/baron/task-newnpx skills add loncadev/baron --skill task-newgit clone --depth 1 https://github.com/loncadev/baronWrote 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/loncadev/baron/task-new)<a href="https://agentmods.dev/skills/loncadev/baron/task-new"><img src="https://agentmods.dev/badge/skills/loncadev/baron/task-new.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.00888 |
| Opus 5 | $0.00041 | $0.00444 |
| Sonnet 5 | $0.00016 | $0.00178 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
task-new 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a work item
Turn the user's request into a work item that is actually actionable by whoever picks it up — not
a bare title — then run the task-new recipe as ONE deterministic call. Creation only; it does not
branch or change your checkout (that's /task-start).
Steps
-
Infer the type role from the wording: defect/broken/error →
bug; a user-facing capability →story; a concrete engineering step →task. If ambiguous, ask viaAskUserQuestion(task / bug / story). -
Reach a well-specified item BEFORE creating — don't open a hollow title. A title-only issue is guesswork for the next person. Decide how much you already have:
- The context already settles it — the conversation made the decisions and now says "make a task for it", or the user's message already carries the what + why (+ repro for a bug). Then synthesize the body from that context; don't re-ask what you already know.
- The input is thin — just a short title, no substance. Then grill to decision-saturation
with
AskUserQuestionbefore creating: ask only the few questions that actually change the body — typically what problem / goal, why now / value, what "done" means (acceptance), and for a bug the repro → expected → observed. Stop as soon as you could write a body someone else could act on; don't interrogate past that. - Respect a deliberate quick capture. If the user says "just create it" / "only the title for now", create with what you have — a note in the body that detail is TBD, not a wall of questions.
Compose the gathered detail into a clear body (markdown). This is what makes the item useful; the title alone never is.
-
Resolve the parent (a dangling item gets lost):
bug/taskbelong under a story; astorybelongs under an epic.- Find candidates with
baron_issue_read op=query(typeRole: "story"or"epic") and offer the best 2-3 viaAskUserQuestion, plus "no parent". Never invent a parent id. - On providers without native hierarchy the parent is emulated/degraded per policy — Baron's job.
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 First seen · 63 lines · 82 tokens per session scan A 611a5f279df9
task-new is a skill published in the GitHub repository loncadev/baron (1 stars, last pushed 13d ago), licensed Apache-2.0. It adds 82 tokens to every session and 888 once invoked, about $0.0004 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-31.
Other skills, from other repositories
csharp-bootstrap
Harness fixture bootstrap producer for the csharp project language. Minimal shape — exercises BootstrapDispatch + BootstrapRound, not real bootstrap output.
generic-bootstrap
Harness fixture bootstrap producer for the generic project language. Minimal shape — exercises BootstrapDispatch + BootstrapRound, not real bootstrap output.
coding-agent-master
Harness fixture master skill for coding pipelines. Intentionally minimal — handler-chain shape only, not real master behaviour.
node-bootstrap
Harness fixture bootstrap producer for the node project language. Minimal shape — exercises BootstrapDispatch + BootstrapRound, not real bootstrap output.
python-bootstrap
Harness fixture bootstrap producer for the python project language. Minimal shape — exercises BootstrapDispatch + BootstrapRound, not real bootstrap output.
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.