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 ils15/pantheon-legacy --skill task-systemgit clone --depth 1 https://github.com/ils15/pantheon-legacyWrote 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/ils15/pantheon-legacy/task-system)<a href="https://agentmods.dev/skills/ils15/pantheon-legacy/task-system"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/task-system/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/ils15/pantheon-legacy/task-system"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/task-system.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.00025 | $0.01987 |
| Opus 5 | $0.00013 | $0.00993 |
| Sonnet 5 | $0.00005 | $0.00397 |
| Haiku 4.5 | $0.00003 | $0.00199 |
Grade C, and why
task-system scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .pantheon/tasks/T-*.json How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task System — File-Backed Task Management
Use this skill for complex work with multiple interdependent tasks. Tasks are stored as JSON files, survive session restarts, and support automatic parallel execution based on dependency graphs.
When to Use
| Scenario | Use |
|---|---|
| 1-2 simple tasks | TodoWrite |
| 3+ tasks with dependencies | Task System |
| Tasks need to survive restart | Task System |
| Parallel execution needed | Task System |
| Multiple agents collaborating | Task System |
Task Schema
{
"id": "T-001",
"subject": "Build frontend",
"description": "Implement ReviewCard component with mocked data",
"status": "pending",
"activeForm": "Building ReviewCard component",
"blockedBy": [],
"blocks": ["T-003"],
"owner": "Aphrodite",
"metadata": {},
"threadID": "session-abc",
"timeout_ms": 180000,
"retry_policy": { "count": 3, "backoff": "exponential" },
"fallback_agent": "talos",
"partial_ok": false,
"session_id": null,
"session_resume": null
}
| Field | Type | Required | Description |
|---|---|---|---|
id |
string | Yes | Auto-generated: T-{sequential} |
subject |
string | Yes | Imperative: "Run tests", "Build component" |
description |
string | Yes | Detailed description of the task |
status |
enum | Yes | pending, in_progress, completed, deleted |
activeForm |
string | No | Present continuous: "Running tests" |
blockedBy |
string[] | Yes | Task IDs that must complete first |
blocks |
string[] | Yes | Task IDs that this task blocks |
owner |
string | No | Agent name responsible |
metadata |
object | No | Additional context |
threadID |
string | Yes | Session ID (auto-set) |
timeout_ms |
integer | No | Timeout in milliseconds for this task (default: 120000 = 2min). 0 = no timeout |
retry_policy |
object | No | { count: number, backoff: "exponential"|"fixed" }. Default: { count: 3, backoff: "exponential" } |
fallback_agent |
string | No | Agent name to use if all retries fail. Default: null (escalate to Zeus) |
partial_ok |
boolean | No | If true, partial results are acceptable on timeout. Default: false |
session_id |
string | No | Alias of the session running this task (e.g. "hermes-1"). Set automatically |
session_resume |
string | No | Session alias to resume instead of starting fresh (e.g. "hermes-1") |
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.
- 8d ago First seen · 263 lines · 25 tokens per session scan C bf2bb607f7ea
task-system is a skill published in the GitHub repository ils15/pantheon-legacy (10 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 1,987 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.