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/hamchowderr/braynee/tasksnpx skills add hamchowderr/braynee --skill tasksgit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00081 | $0.01030 |
| Opus 5 | $0.00041 | $0.00515 |
| Sonnet 5 | $0.00016 | $0.00206 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tasks (TaskNotes via mtn)
Manage tasks through mtn — the standalone TaskNotes CLI. It reads and
writes the task markdown files directly through mdbase.
There is no HTTP API and no server. mtn operates on files, so it works
whether or not Obsidian is running, with no port and no auth token. (TaskNotes
does ship an HTTP API, but braynee deliberately does not use it — the CLI is
the supported path. Never reach for localhost:8080/REST here.)
mtn is configured once (~/.config/mdbase-tasknotes/config.json) with
collectionPath pointing at the vault, so commands need no path argument.
Reading tasks
Always pass --json when you need to reason over results.
mtn list --json # all tasks (open + done), structured
mtn list --status open --json # only open
mtn list --overdue --json # overdue
mtn list --priority high --json # by priority
mtn list --tag task --json # by tag
mtn list --due 2026-05-30 --json # by due date
mtn search "<query>" --json # full-text search
mtn show "<title-or-path>" # full detail of one task
mtn stats # counts by status/priority
Each list --json item has: path, title, status, priority, due,
scheduled, projects (["[[Project]]"]), contexts (["@ctx"]),
timeEstimate (minutes), tags, recurrenceAnchor.
Creating tasks
mtn create parses natural language — dates, priority, project, contexts,
and tags are extracted from the text. Write the task so it is self-contained:
enough context that it can be picked up later without the conversation.
# NLP: "tomorrow", "high", "+Project", "@context", "#tag" are all parsed
mtn create "Draft the Q3 proposal tomorrow high +ClientWork @writing"
mtn create "Call the dentist next monday"
Confirm what was created by echoing the resulting title back from
mtn list --status open --limit 1 --json.
Completing / updating
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.
- yesterday First seen · 103 lines · 81 tokens per session scan A c0c64ee922b5
tasks is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 5d ago), licensed MIT. It adds 81 tokens to every session and 1,030 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…