Borrowing it
Nothing to install: this file belongs to adrian-d-hidalgo/nestjs-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adrian-d-hidalgo/nestjs-mcp-server/main/.claude/skills/task-workspace/SKILL.mdgit clone --depth 1 https://github.com/adrian-d-hidalgo/nestjs-mcp-serverWrote 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/adrian-d-hidalgo/nestjs-mcp-server/task-workspace)<a href="https://agentmods.dev/skills/adrian-d-hidalgo/nestjs-mcp-server/task-workspace"><img src="https://agentmods.dev/badge/skills/adrian-d-hidalgo/nestjs-mcp-server/task-workspace/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/adrian-d-hidalgo/nestjs-mcp-server/task-workspace"><img src="https://agentmods.dev/badge/skills/adrian-d-hidalgo/nestjs-mcp-server/task-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.03254 |
| Opus 5 | $0.00036 | $0.01627 |
| Sonnet 5 | $0.00014 | $0.00651 |
| Haiku 4.5 | $0.00007 | $0.00325 |
Grade A, and why
task-workspace 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 9d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill owns where things live and who writes them. It does not own the SPEC's content —
that belongs to the spec-driven skill.
That is a deliberate line, not an omission. spec.md and test-plan.md answer what must be done
and stay true across sessions. An execution plan answers how, right now, against this working
tree — it is stale the moment the code moves, and a stale plan on disk is worse than no plan,
because a later session reads it as current. The durable half of the pipeline is the specification
and the evidence; the plan is the ephemeral bridge between them.
.project/
tasks/
README.md # what this folder is (committed nowhere — .project is gitignored)
issue-96/
spec.md # the technical SPEC — written by /specification
test-plan.md # the QA / acceptance plan — written by /specification
verification.md # AC → evidence record — written by /develop
notes.md # findings, dead ends — written by any stage, append-only
issue-109/
...
Four files, and no execution plan among them — see <WhatIsDeliberatelyNotHere>.
Create the directory lazily — only when a stage actually has something to write. An empty
issue-N/ directory is noise that implies work that never happened.
Never create a file with only its template headings. A verification.md full of unfilled
placeholders reads, to a later session, as work that was done and found nothing. If a stage has
nothing to record yet, it writes nothing.
The split is by shelf life: /specification writes what stays true (the spec, the QA plan),
/develop writes what was found (the evidence, the notes). The execution plan sits between them
and is stale on contact with a changed working tree, so it stays in the conversation.
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.
- 9d ago First seen · 186 lines · 71 tokens per session scan A 108e787066d8
task-workspace is a skill published in the GitHub repository adrian-d-hidalgo/nestjs-mcp-server (38 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 3,254 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…