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/tonycasey/lisa/tasksnpx skills add TonyCasey/lisa --skill tasksgit clone --depth 1 https://github.com/TonyCasey/lisaWrote 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/tonycasey/lisa/tasks)<a href="https://agentmods.dev/skills/tonycasey/lisa/tasks"><img src="https://agentmods.dev/badge/skills/tonycasey/lisa/tasks.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 | $0.00036 | $0.00406 |
| Opus 5 | $0.00018 | $0.00203 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
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 4d 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.
What it actually says
Purpose
Model-neutral helper to add/list tasks in Graphiti MCP so any agent can keep a shared task board.
Triggers
Use when the user says: "add a task", "list tasks", "load tasks", "task status".
How to use
- List:
lisa tasks list --cache [--group <id>] [--limit 20] [--all|--since today] - Add:
lisa tasks add "<task text>" [--status todo|doing|done] [--tag foo] [--group <id>] --cache - Defaults: reads ${GRAPHITI_ENDPOINT} from
.lisa/.env(written by init); group ID is automatically derived from the project folder path. List defaults to--since todayunless--allor--sinceis provided. - Cache fallback: writes/reads
cache/tasks.logwhen--cacheis passed, returning last cached result on MCP failure. - Keep prompts model-neutral; models only orchestrate CLI commands and summarize JSON output.
I/O contract (examples)
- List:
{ status: "ok", action: "list", tasks: [...] } - Add:
{ status: "ok", action: "add", task: { text, status, group } } - Fallback:
{ status: "fallback", error, fallback: <cached object> }
Cross-model checklist
- Claude: concise instructions; avoid role tokens; keep outputs small.
- Gemini: explicit commands and minimal formatting.
Notes
- All commands use the
lisaCLI binary — no scripts to run directly. - Tasks are stored via Graphiti MCP
add_task/list_tasks.
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.
- 4d ago First seen · 31 lines · 36 tokens per session scan A 267a73e18154
tasks is a skill published in the GitHub repository TonyCasey/lisa (9 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 406 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-31.
Other skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
team
Invite humans into a workspace, propose collaborators for a project, and inspect the current human team. Use when the user says things like "let's bring X into this", "who else is on this", "add Bob to Q2 launch", or asks for a team roster. NEVER mints invites silently — the human must press a button.