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 ithinkihaveacat/dotfiles --skill taskgogit clone --depth 1 https://github.com/ithinkihaveacat/dotfilesWrote 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/ithinkihaveacat/dotfiles/taskgo)<a href="https://agentmods.dev/skills/ithinkihaveacat/dotfiles/taskgo"><img src="https://agentmods.dev/badge/skills/ithinkihaveacat/dotfiles/taskgo/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/ithinkihaveacat/dotfiles/taskgo"><img src="https://agentmods.dev/badge/skills/ithinkihaveacat/dotfiles/taskgo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 52 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Rogue Agent · line 74 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00071 | $0.04247 |
| Opus 5.5 | $0.00028 | $0.01699 |
| Sonnet 5.5 | $0.00014 | $0.00849 |
| Haiku 4.5 | $0.00007 | $0.00425 |
Grade A, and why
taskgo 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taskgo
taskgo manages a private control repository spanning multiple projects. Humans read current Markdown; agents edit it, operate Git, reconstruct history, and generate summaries.
Tool Execution
taskgo is bundled in scripts/taskgo within this skill directory. Commands
operate on a fixed control repository root, resolved in this order:
--root DIR/-R DIR(must appear before the command)- the
TASKGO_ROOTenvironment variable - the default
~/.projects
Execution resolution never depends on the current working directory. Run
taskgo doctor to see the resolved root. To execute the tool:
- Optimal (
$PATH):taskgo <command> - Dynamic anchor:
<skill-dir>/scripts/taskgo <command>
Core Invariants
- Current Truth:
HEADdescribes current belief. Git owns administrative history. Avoid accumulating historical journals in Markdown. - Data Segregation: Private tracker information must not implicitly flow
into linked public/shared artifacts.
Conversation:trailers and session URLs belong strictly in the control repository metadata. Artifact path references prefer$HOME-relative form (~/...). - Link Portability: Internal links must be standard relative Markdown (no
file://). External references must be network URLs (https://) or unlinked monospace text. - STATUS.md: This is the self-contained projection of current operational state. Reading it directly answers status and next steps.
- Commit Authority: The
<!-- taskgo:allow-local-commits -->marker in the control repo'sAGENTS.mdgrants standing authority for guarded local checkpoint commits (create,checkpoint,fix). Never rewrite artifact history. - No Administrative Metadata: Do not invent metadata fields like
created,updated, orblocked_sincein YAML frontmatter. Git owns administrative history. Do not duplicateProject:,Task:, orEvent:trailers.
Tasks
IDs are globally unique TASK-XXXXX (five hex digits). Task files are
tasks/TASK-XXXXX-<slug>.md. Pass --slug (max 32 chars) when creating tasks
if the title is long.
What ships with it
23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- completions/taskgo.fish 14 KB
- references/activity-reports.md 4.7 KB
- references/command-index.md 26 KB
- references/export.md 2.8 KB
- references/mcp.md 24 KB
- references/model.md 30 KB
- references/workflows.md 6.9 KB
- scripts/taskgo 413 KB
- tests/auth-check 18 KB
- tests/compare-cli 11 KB
- tests/make-synthetic 3.5 KB
- tests/mcp-call 2.1 KB
- tests/protocol-check 4.6 KB
- tests/test-taskgo-apply 31 KB
- tests/test-taskgo-crud 26 KB
- tests/test-taskgo-edge-cases 29 KB
- tests/test-taskgo-formatting-schema 21 KB
- tests/test-taskgo-graph 11 KB
- tests/test-taskgo-handoff-adr 37 KB
- tests/test-taskgo-mcp 24 KB
- tests/test-taskgo-mcp-write 65 KB
- tests/test-taskgo-scheduling-check 21 KB
- tests/test-taskgo-sync-checkpoint 9.4 KB
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 6bae53e00c45
- 4d ago Changed · +2 lines · -2 tokens per session 2669000f5f73
- 5d ago Changed · +11 lines 8e3cc2ead9c8
- 6d ago Changed · +31 lines 228487aa78ff
- 7d ago Changed · +30 lines 2f5e07bf1fe0
- 12d ago Changed · +17 lines d316b7939567
- 13d ago Changed f9d97a3c5b8f
- 14d ago Changed · +10 lines 25c35cabf488
- 15d ago Changed · +5 lines c8e2eaf82468
- 16d ago First seen · 226 lines · 73 tokens per session scan A 3309a26efc06
taskgo is a skill published in the GitHub repository ithinkihaveacat/dotfiles (48 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 4,247 once invoked, about $0.0003 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-30.
Other skills, from other repositories
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
herdr
Use when the user mentions herdr or is working inside a herdr pane and wants to save/restore a pane layout, change herdr's theme, prefix or other preferences on this host only, start or check on an agent in another herdr pane, add, turn off or open a herdr plugin (file viewer, keybindings), or asks why the herdr…
devlog
Keep DEVLOG.md up to date and use it to resume project context in the user's personal developer-log style. Use when the user asks to update, write, continue, summarize, resume, catch up from, or maintain @DEVLOG.md / DEVLOG.md after or before a work session, or asks to capture what they did, learned, decided, got…
there-there
Manage There There helpdesk tickets, contacts, and channels using the there-there CLI. Use when the user wants to list, view, reply to, search, or manage tickets; assign team members; manage tags; view contacts; or interact with there-there.app from the command line.
master-build
Keep a stable, installed build of a desktop app that the owner can use and test while agents keep working in the repository. Use when agents building or launching the app are getting in the owner's way, when the working tree is often mid edit and does not compile, when asked for a "master build", or when the owner…
morning-coffee
Prepare a source-read-only daily engineering brief with GitHub pull requests, today's Google Calendar agenda, current-quarter Transport planning links, incident.io on-call and incident context, RFCs needing review, ranked daily priorities, and previous-working-day activity. Use for morning check-ins, daily planning…