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/felipejj/fullstack-pipeline/tasksnpx skills add felipeJJ/fullStack-pipeline --skill tasksgit clone --depth 1 https://github.com/felipeJJ/fullStack-pipelineWhat 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.00051 | $0.00656 |
| Opus 5 | $0.00026 | $0.00328 |
| Sonnet 5 | $0.00010 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00066 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Registry
Local-first registry: fast to search, human-readable plans, no digging through git log. Lives in .claude/pipeline/ of the project. All commands run through the CLI (cliPath in .claude/pipeline/profile.json): node <cliPath> <command>.
Commands
| Command | Purpose |
|---|---|
new "<title>" --type=improvement|bugfix --level=N |
Create task + plan file, prints TASK-<id> and plan path |
list [--status=planned|in-progress|ready|done] |
Table of tasks |
search "<term>" |
Case-insensitive search across titles and plan file contents |
show <id> |
Full record: status, level, commit, attempts, plan path |
start <id> |
Mark in progress (one active task at a time) |
tdd-red <id> / tdd-skip <id> --reason="..." |
Confirm failing tests exist / justify absence — unblocks the TDD guard |
ready <id> |
Checklist done, cleared to commit — unblocks the commit gate |
done <id> --commit=<hash> |
Close task (the post-commit hook usually does this) |
note <id> "<text>" |
Append a timestamped note (decisions, context) |
rework <id> --area=X --reason="..." |
Record a review rejection / rework attempt (telemetry + attempt limit) |
usage <id> --json='[{"model":"sonnet","input":N,"output":N}]' |
Attach token usage per model (from OTel or /cost) for cost estimation |
report [--since=YYYY-MM-DD] |
Per-task wall time / attempts / est. cost + aggregation per model matrix (the A/B cost-comparison view) |
index |
Regenerate INDEX.md (auto-run by mutating commands) |
Layout
tasks.json— the structured registry (ids, status, level, commit hash, attempts, timestamps).plans/TASK-<id>.md— the human file: discovery Q&A, mini-tasks, contract, decisions. This is what the user reads to evaluate a plan before authorizing execution.INDEX.md— generated view, newest first. Never edit by hand.
Retroactive registration
A hotfix committed outside the pipeline still gets registered: new with --type=bugfix, then done --commit=<hash>. The commit gate makes this rare by construction, but when it happens (gate skipped via PIPELINE_SKIP_GATE=1), register it as soon as noticed.
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 · 37 lines · 51 tokens per session scan A 97e7d256223e
tasks is a skill published in the GitHub repository felipeJJ/fullStack-pipeline (1 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 656 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
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…