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 DavidROliverBA/ArchitectKB --skill taskgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/task)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/task"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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/davidroliverba/architectkb/task"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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.00000 | $0.00694 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
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 9d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/task
Quick-create a task linked to a project, optionally with subtasks.
Usage
/task <title>
/task <title> for <project>
/task <title> due <date>
/task <title> priority high
/task <title> with subtasks
Examples
/task Review ADR draft
/task Complete security assessment for MyProject due Friday
/task Update architecture diagram priority high for CloudMigration
/task Platform Migration Tasks with subtasks
Instructions
-
Parse the command for:
- title: Task description (required)
- project: Project to link (after "for")
- dueBy: Hard deadline (after "due") - parse natural language
- doDate: When to start working (after "start" or "do")
- priority: high/medium/low (after "priority")
- subtasks: If "with subtasks" mentioned, prompt for subtask titles
-
Defaults:
- priority: medium
- dueBy: null
- doDate: null
- project: null (or infer from recent context)
- parentTask: null
- subtasks: []
-
Generate filename:
Task - {{title}}.md -
Create task in vault root:
---
type: Task
title: {{ title }}
created: {{ DATE }}
modified: {{ DATE }}
completed: false
priority: {{ priority }}
doDate: {{ do_date or null }}
dueBy: {{ due_date or null }}
project: {{ project_link or null }}
assignedTo: ["[[Your Name]]"]
parentTask: {{ parent_task_link or null }}
subtasks: {{ subtask_links or [] }}
tags: []
---
# {{title}}
## Description
{{title expanded if needed}}
## Acceptance Criteria
- [ ]
## Subtasks
{{list of subtask links if any}}
## Notes
## Related
{{project link if provided}}
-
If project provided:
- Format as wiki-link:
"[[Project - MyProject]]" - Fuzzy match project name if partial
- Format as wiki-link:
-
If due date provided:
- Parse natural language: "Friday" → next Friday's date
- "tomorrow" → tomorrow's date
- "next week" → Monday of next week
- Format as YYYY-MM-DD
-
If subtasks requested:
- Prompt for subtask titles (or parse from context)
- Create each subtask as a separate Task note
- Link subtasks in parent's
subtasksarray - Set each subtask's
parentTaskfield to parent
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.
- 9d ago First seen · 116 lines · 0 tokens per session scan A abcd5c7b4891
task is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 694 tokens. 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-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.