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 Joaonic/agentkit --skill posttask-workspace-lintgit clone --depth 1 https://github.com/Joaonic/agentkitWrote 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/joaonic/agentkit/posttask-workspace-lint)<a href="https://agentmods.dev/skills/joaonic/agentkit/posttask-workspace-lint"><img src="https://agentmods.dev/badge/skills/joaonic/agentkit/posttask-workspace-lint/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/joaonic/agentkit/posttask-workspace-lint"><img src="https://agentmods.dev/badge/skills/joaonic/agentkit/posttask-workspace-lint.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.00045 | $0.00610 |
| Opus 5.5 | $0.00018 | $0.00244 |
| Sonnet 5.5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
posttask-workspace-lint 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.
What it actually says
Posttask Workspace Lint
Objetivo
No monorepo YourProject, qualidade local vive no subprojeto. Antes de declarar conclusão, rodar os comandos que o próprio módulo define (README, package.json, pom.xml), agrupados por pasta tocada.
Quando é obrigatório
- Qualquer alteração sob
apps/<serviço>/,web/<app>/, oulibraries/<lib>/. - Consultar
AGENTS.mde README do subprojeto quando existirem (40-submodule-governance.mdc).
Detecção de escopo
- A partir de
git diff, lista de ficheiros, ou instrução explícita do utilizador → extrair prefixos de primeiro nível (apps/foo,web/bar, …). - Agrupar por subprojeto (segmento imediato após
apps/,web/,libraries/). - Mudanças só em
docs/,.cursor/, scripts na raiz sem tocar código de app → pode não haver módulo Maven/Yarn; marcar comandos comon/acom motivo.
Comandos padrão (sobrescrever pelo README local)
| Área | Onde executar | Comandos típicos |
|---|---|---|
| Backend Java | Diretório com pom.xml do serviço |
./mvnw verify ou ./mvnw test |
| Library Java | Raiz da biblioteca | ./mvnw verify / ./mvnw test |
| Frontend | Raiz do app (package.json) |
yarn lint, yarn build, yarn test (se scripts existirem) |
Se só uma classe ou pacote mudou e verify for pesado, pode usar alvo restrito desde que o README/CI do projeto aceite (ex.: ./mvnw -pl modulo test quando multi-módulo).
Relatório obrigatório
Tabela:
| Subprojeto | Diretório | Comando | Resultado (pass / fail / n/a) | Notas |
- Qualquer
failbloqueia conclusão (alinhado aposttask/30-posttask.mdc). n/asó com razão explícita (ex.: alteração só em Markdown na raiz).
Relação com outras skills
posttask— gate global de evidência; esta skill especializa por workspace no monorepo.lint-fix— usar quando falhas forem corrigíveis por autofix seguro no escopo tocado.
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 · 46 lines · 45 tokens per session scan A aef584c761f9
posttask-workspace-lint is a skill published in the GitHub repository Joaonic/agentkit (2 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 610 once invoked, about $0.0002 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.