Borrowing it
Nothing to install: this file belongs to Codename-11/SubFrame. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Codename-11/SubFrame/main/.agents/skills/sub-tasks/SKILL.mdgit clone --depth 1 https://github.com/Codename-11/SubFrameWrote 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/codename-11/subframe/sub-tasks)<a href="https://agentmods.dev/skills/codename-11/subframe/sub-tasks"><img src="https://agentmods.dev/badge/skills/codename-11/subframe/sub-tasks/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/codename-11/subframe/sub-tasks"><img src="https://agentmods.dev/badge/skills/codename-11/subframe/sub-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 101 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.00032 | $0.00776 |
| Opus 5.5 | $0.00013 | $0.00310 |
| Sonnet 5.5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
sub-tasks 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SubFrame Sub-Tasks
Manage the project's Sub-Task system. Sub-Tasks are SubFrame's project task tracking stored as individual markdown files in .subframe/tasks/.
Dynamic Context
Current task index:
!cat .subframe/tasks.json 2>/dev/null || echo "No tasks.json found"
Instructions
Argument: $ARGUMENTS
Task File Format
Each task is a markdown file in .subframe/tasks/ with YAML frontmatter:
---
id: task-abc123
title: My task title
status: pending
priority: medium
category: feature
description: What needs to be done
userRequest: The user's original words
acceptanceCriteria: How to verify completion
blockedBy: []
blocks: []
createdAt: 2024-01-01T00:00:00.000Z
updatedAt: 2024-01-01T00:00:00.000Z
completedAt: null
---
## Notes
Session notes go here.
## Steps
- [ ] Step one
- [x] Step two (completed)
Operations
List tasks
Read .subframe/tasks.json for the index overview, or glob .subframe/tasks/*.md and read frontmatter.
Get task details
Read the specific .subframe/tasks/<id>.md file.
Start a task (pending → in_progress)
Edit the task's frontmatter: set status: in_progress and update updatedAt.
Complete a task
Edit the task's frontmatter: set status: completed, set completedAt to current ISO timestamp, update updatedAt.
Add a new task
Create a new .subframe/tasks/<id>.md file with:
- Generate id:
task-+ 8 random alphanumeric chars - Set
status: pending,createdAtandupdatedAtto current ISO timestamp completedAt: null- Include all required fields in frontmatter
Update a task
Edit the frontmatter fields as needed. Always update updatedAt.
Archive completed tasks
Move completed .md files to .subframe/tasks/archive/YYYY/ (create directory if needed).
After Any Write Operation
Regenerate the .subframe/tasks.json index by reading all .subframe/tasks/*.md files (excluding archive/) and building the JSON structure with tasks grouped by status (pending, inProgress, completed).
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.
- 1mo ago First seen · 108 lines · 32 tokens per session scan A f62f630dc1a0
sub-tasks is a skill published in the GitHub repository Codename-11/SubFrame (10 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 776 once invoked, about $0.0001 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-31.
Other skills, from other repositories
ox-cli-session-review
Audit every session in the project ledger for quality, then offer cleanup and regeneration. Carries the operational knowledge from the 2026-04-25 cleanup (the cache-only invariant and a failure-mode watch-list) that no single ox subcommand backs. Use when the user asks to "review the ledger sessions", "audit session…
ox-cli-session-stop
Stop recording and save this agent session to the project ledger.
intuitive-shape
Shape unsettled product ideas into bounded bets before planning; excludes settled fixes and approved execution.
intuitive-doc
Maintain README.md, ARCHITECTURE.md, STATUS.md, and docs/human/ when they drift or need cleanup.
ox-cli-status
Check SageOx project status including authentication, sync, and daemon health.
ox-cli-session-abort
Abort a session, discarding all local data without uploading to the ledger.