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 bcosta19/mcp-gestao-tarefas --skill gestao-tarefasgit clone --depth 1 https://github.com/bcosta19/mcp-gestao-tarefasWrote 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/bcosta19/mcp-gestao-tarefas/gestao-tarefas)<a href="https://agentmods.dev/skills/bcosta19/mcp-gestao-tarefas/gestao-tarefas"><img src="https://agentmods.dev/badge/skills/bcosta19/mcp-gestao-tarefas/gestao-tarefas/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/bcosta19/mcp-gestao-tarefas/gestao-tarefas"><img src="https://agentmods.dev/badge/skills/bcosta19/mcp-gestao-tarefas/gestao-tarefas.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.00053 | $0.01107 |
| Opus 5 | $0.00026 | $0.00553 |
| Sonnet 5 | $0.00011 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
gestao-tarefas 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 12d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocolo e Boas Práticas do MCP Gestão de Tarefas
Este documento orienta o agente sobre as regras de negócio, tomada de decisão e sequência correta de chamadas das ferramentas do servidor MCP Gestão de Tarefas.
1. Regra de Ouro: Detecção de Contexto Obrigatória
Antes de realizar qualquer operação de leitura ou escrita de demandas/subtarefas:
- Chame sempre
obter_contexto_projetopassando o diretório do projeto (diretorio_path). - Avalie o retorno do campo
mcp_ativo:- Se
mcp_ativo === false: O projeto atual é externo, pessoal ou não identificado. NÃO crie ou altere demandas no Gestão de Tarefas. Informe o usuário de forma respeitosa que o projeto não está vinculado ao sistema. - Se
mcp_ativo === true: Prossiga utilizando oprojeto.id, o nome do projeto e asprint_atualdetectada.
- Se
2. Prevenção de Duplicações e Poluição
Evite criar demandas repetidas ou rascunhos sem necessidade:
- Consulta prévia: Antes de propor criar uma nova demanda, chame
listar_demandas_ativascom oprojeto_iddo projeto atual para consultar as demandas em andamento. - Preferência por Subtarefas:
- Se o desenvolvedor estiver executando uma tarefa técnica referente a uma demanda já existente (ex: "Ajustes nas telas", "Correções gerais", "Implementação de módulo"), crie subtarefas vinculadas a essa demanda via
criar_subtarefa. - Crie uma nova demanda (
criar_demanda) apenas quando:- Tratar-se de uma nova funcionalidade / iniciativa de escopo separado;
- O usuário solicitar expressamente a criação de uma nova demanda.
- Se o desenvolvedor estiver executando uma tarefa técnica referente a uma demanda já existente (ex: "Ajustes nas telas", "Correções gerais", "Implementação de módulo"), crie subtarefas vinculadas a essa demanda via
3. Padrões para Criação e Atualização de Demandas
Ao usar criar_demanda ou atualizar_demanda:
- Título: Claro, conciso e semântico (ex:
feat(auth): adiciona login sso,fix(ui): corrige overflow na listagem). - Descrição (
descricao): Formate sempre em HTML estruturado (<p>,<ul>,<li>,<strong>,<code>). - Data Limite (
data_limite): Obrigatória no formatoYYYY-MM-DD. Por padrão, utilize a data de fim da sprint ativa ou a data limite acordada. - Sprint (
sprint_id): Vincule à sprint ativa do projeto (sprint_atual.id). - Responsável (
responsavel_id): Atribua ao ID do colaborador que está desenvolvendo (identificado no contexto ou nas demandas ativas). - Prioridade e Impacto: Use
'Alta','Média'ou'Baixa'para prioridade, e'alto','medio'ou'baixo'para impacto.
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.
- 12d ago First seen · 66 lines · 53 tokens per session scan A 615382d8d487
gestao-tarefas is a skill published in the GitHub repository bcosta19/mcp-gestao-tarefas (0 stars, last pushed 21d ago), licensed MIT. It adds 53 tokens to every session and 1,107 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.