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/marcusrbrown/systematic/todosnpx skills add marcusrbrown/systematic --skill todosgit clone --depth 1 https://github.com/marcusrbrown/systematicWhat 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.00063 | $0.02224 |
| Opus 5 | $0.00032 | $0.01112 |
| Sonnet 5 | $0.00013 | $0.00445 |
| Haiku 4.5 | $0.00006 | $0.00222 |
Grade A, and why
todos 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File-Based Todo Tracking
Overview
The .context/systematic/todos/ directory is a file-based tracking system for code review feedback, technical debt, feature requests, and work items. Each todo is a markdown file with YAML frontmatter. This skill covers the full lifecycle in three sections: Create (new todos), Triage (review pending todos for approval), and Resolve (batch-implement approved todos).
Legacy support: Always check both
.context/systematic/todos/(canonical) andtodos/(legacy) when reading. Write new todos only to the canonical path. This directory has a multi-session lifecycle -- do not clean it up as scratch.
Directory Paths
| Purpose | Path |
|---|---|
| Canonical (write here) | .context/systematic/todos/ |
| Legacy (read-only) | todos/ |
File Naming Convention
{issue_id}-{status}-{priority}-{description}.md
- issue_id: Sequential number (001, 002, ...) -- never reused
- status:
pending|ready|complete - priority:
p1(critical) |p2(important) |p3(nice-to-have) - description: kebab-case, brief
Example: 002-ready-p1-fix-n-plus-1.md
File Structure
Each todo has YAML frontmatter and structured sections. Use the todo template included below when creating new todos.
---
status: ready
priority: p1
issue_id: "002"
tags: [rails, performance]
dependencies: ["001"] # Issue IDs this is blocked by
---
Required sections: Problem Statement, Findings, Proposed Solutions, Recommended Action (filled during triage), Acceptance Criteria, Work Log.
Optional sections: Technical Details, Resources, Notes.
Integration with Workflows
| Trigger | Flow |
|---|---|
| Code review | /ce:review -> Findings -> /systematic:todos (Triage section) -> Todos |
| Autonomous review | /ce:review mode:autofix -> Residual todos -> /systematic:todos (Resolve section) |
| Code TODOs | /systematic:todos (Resolve section) -> Fixes + Complex todos |
| Planning | Brainstorm -> Create todo -> Work -> Complete |
What ships with it
1 file 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.
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 · 240 lines · 63 tokens per session scan A 0a12d0d78b3e
todos is a skill published in the GitHub repository marcusrbrown/systematic (24 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 2,224 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-08-30.
Other skills, from other repositories
plan-protocol
Guidelines for creating and managing implementation plans with citations.
plan-review
Criteria for reviewing implementation plans against quality standards.
code-review
Comprehensive code review methodology with severity classification and confidence thresholds.
code-philosophy
Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Understand deeply to ensure code guides data naturally and prevents errors.
frontend-philosophy
Visual & UI philosophy (The 5 Pillars of Intentional UI). Understand deeply to avoid "AI slop" and create distinctive, memorable interfaces.
opencode-ensemble
Use when coordinating multiple coding agents, delegating independent software work, managing OpenCode Ensemble teams, choosing teammate roles or models, reviewing teammate output, or deciding whether parallel execution is appropriate.