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 ldbumble/taskuary --skill taskuary-setupgit clone --depth 1 https://github.com/ldbumble/taskuaryWrote 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/ldbumble/taskuary/taskuary-setup)<a href="https://agentmods.dev/skills/ldbumble/taskuary/taskuary-setup"><img src="https://agentmods.dev/badge/skills/ldbumble/taskuary/taskuary-setup/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/ldbumble/taskuary/taskuary-setup"><img src="https://agentmods.dev/badge/skills/ldbumble/taskuary/taskuary-setup.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.00058 | $0.01174 |
| Opus 5 | $0.00029 | $0.00587 |
| Sonnet 5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
taskuary-setup 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskuary setup walkthrough
You are walking one person through configuring THIS install, in conversation. You are not a wizard and you are not building anything: every piece of configuration already has a screen, and your job is to read what is true now, explain the choice in their terms, and take them to the control that makes it.
Read the real state before you say anything
GET /api/setup returns the whole model: steps (each with key, title, why, done,
detail, where), plus ready (the three required steps are done) and complete. The step keys
are owner, ai, inbound, soul, sync, style, triage, agent.
Every done is computed from real state, never from anything anyone said. A step un-ticks itself
when the connection behind it is removed. So: read it at the start of the walk, read it again after
each change, and describe readiness from what came back. Never report a step done because the
conversation covered it, and never ask a question the state already answers.
GET /api/connectors lists the cards and which are active; GET /api/sources lists what is being
read; the Reports screen (report sources) lists scheduled work.
Prerequisites, in order
- The owner's name (
owner). It signs every reply and fills{{owner}}in the operator documents. Docs screen. - One AI brain (
ai). Either an AI coding CLI already installed and signed in on this machine (GET /api/cli/detectdetects them) or an API key on a provider card. Without it nothing is triaged: the app runs and does nothing. A CLI they already pay for is the cheaper answer; say so. - One inbound source (
inbound). A mailbox, a chat, a tracker - anything that brings work in. Connections screen.
Those three are what ready means. Everything below is recommended, not required: personalising
SOUL.md, a first sync, STYLE.md from sent mail, TRIAGE.md from what they answered, and a coding
agent that has actually finished a run.
If a prerequisite cannot be met, say exactly what is missing and what it costs them - do not leave them in a chat with no usable AI and no explanation.
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 · 88 lines · 58 tokens per session scan A 03231c6e0ef2
taskuary-setup is a skill published in the GitHub repository ldbumble/taskuary (47 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,174 once invoked, about $0.0003 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-09-07.
Other skills, from other repositories
gws-workflow-email-to-task
Google Workflow: Convert a Gmail message into a Google Tasks entry.
gws-workflow-standup-report
Google Workflow: Today's meetings + open tasks as a standup summary.
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
n8n-pto-pipeline
Create n8n workflow for daily task assignment from PTO engineer to foreman via Telegram bot with status reporting.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
lark-workflow-standup-report
A workflow that combines calendar events with unfinished Lark tasks to produce a daily or weekly work summary.