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/foxfire1st/agents-remember/w-02-light-task-workflownpx skills add Foxfire1st/agents-remember --skill w-02-light-task-workflowgit clone --depth 1 https://github.com/Foxfire1st/agents-rememberWrote 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/foxfire1st/agents-remember/w-02-light-task-workflow)<a href="https://agentmods.dev/skills/foxfire1st/agents-remember/w-02-light-task-workflow"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/w-02-light-task-workflow.svg" alt="Measured on agentmods" 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.00043 | $0.02355 |
| Opus 5 | $0.00022 | $0.01177 |
| Sonnet 5 | $0.00009 | $0.00471 |
| Haiku 4.5 | $0.00004 | $0.00235 |
Grade A, and why
w-02-light-task-workflow 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 6d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
w-02-light-task-workflow Light Task Workflow
This skill is the thin orchestration contract for the in-between case: work that needs a durable task file, an explicit approval gate, distinct implementation examples, and decision tracking, but still fits a single-page implementation plan as a rule of thumb.
Companion Files
workflow.mdtemplate.mdmaster-template.md
When To Use
Use this workflow when:
- the work needs a durable task file, an approval gate, and decision tracking
- the implementation plan can still fit on a single page as a rule of thumb
- the target may be non-code or a small isolated code change, provided the lighter single-page plan remains a good fit
Treat the single-page-plan test as guidance rather than a hard routing rule. When the work outgrows a single page — richer artifacts, broader coordination, or a sprawling plan — escalate to a master + light sub-task series (master-template.md) rather than forcing it into one light task.
Task Artifact
Light-task-workflow maintains one task wrapper folder under <task-root>/, where <task-root> is returned by c-08-ar-coordination-context-resolver for the target repository. The task document is always named task.md inside that wrapper folder.
Naming convention:
- ticket-linked:
YYMMDD_#<number>_<short-slug>/task.md - organic:
YYMMDD_<descriptive-slug>/task.md
Create the wrapper folder at the same time the durable task artifact is created, before any c-09-git-worktree-manager worktree exists. Use template.md as the canonical scaffold. Implementation steps and substeps are tracked with checkboxes, and that checklist is the live execution state during implementation. When code changes are in scope, the task file also carries proposed code examples for each distinct change type so the developer can review the intended implementation shape before approval.
Light-task artifacts use minute-precision timestamps in YYYY-MM-DDTHH:MM format wherever they record task-local dates or times.
What ships with it
3 files 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.
- 6d ago First seen · 118 lines · 43 tokens per session scan A 94abafecbe93
w-02-light-task-workflow is a skill published in the GitHub repository Foxfire1st/agents-remember (27 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 2,355 once invoked, about $0.0002 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
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…