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/luis1amaral/system-task-mcp/system-tasknpx skills add luis1amaral/system-task-mcp --skill system-taskgit clone --depth 1 https://github.com/luis1amaral/system-task-mcpWrote 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/luis1amaral/system-task-mcp/system-task)<a href="https://agentmods.dev/skills/luis1amaral/system-task-mcp/system-task"><img src="https://agentmods.dev/badge/skills/luis1amaral/system-task-mcp/system-task.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.00049 | $0.00596 |
| Opus 5 | $0.00024 | $0.00298 |
| Sonnet 5 | $0.00010 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
system-task 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 2d 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
Tarefas
Argumentos: $ARGUMENTS
Como ler o que veio
#nomeou um nome solto → é o projeto. Tire o#e passe comoproject; a tool aceita o nome como a pessoa fala e devolve as opções se for ambíguo.- sem nada → busca em tudo que o usuário enxerga.
- Palavras de filtro que podem vir junto:
atrasadas/atrasado→completed: falseeto= hojeabertas→completed: falseconcluidas/feitas→completed: truesem dono/sem responsavel→unassigned: true- um nome de pessoa depois de
deou@→assignee(exigeproject)
Qual tool usar
| A pergunta é | Use |
|---|---|
| "quais são as tarefas" | systemtask_tasks_search |
| "como está o projeto" / "quanto falta" | systemtask_project_report — números, não linhas |
| "o que vai dar problema" / "o que está atrasado no projeto" | systemtask_project_risks |
| "quais projetos eu tenho" (o nome não foi dito, ou não bateu) | systemtask_projects_list primeiro |
Prefira uma chamada. tasks_search já tem teto de linhas — não pagine atrás de "tudo".
Como responder
Repasse a tabela da tool e pare. Sem resumo do que a tabela já mostra, sem reordenar, sem inventar prioridade. Se vier o aviso de que bateu no limite, diga em uma linha como filtrar melhor.
Título cortado com … e o usuário quer o texto inteiro → systemtask_task_get com o id.
Feche com uma linha do que dá para fazer em seguida (concluir, adiar, atribuir, mover), citando o número da tarefa.
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.
- 2d ago First seen · 46 lines · 49 tokens per session scan A 5477e16145e8
system-task is a skill published in the GitHub repository luis1amaral/system-task-mcp (0 stars, last pushed 18d ago), licensed MIT. It adds 49 tokens to every session and 596 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…