Borrowing it
Nothing to install: this file belongs to jpicklyk/task-orchestrator. 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/jpicklyk/task-orchestrator/main/.claude/skills/add-component/SKILL.mdgit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote 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/jpicklyk/task-orchestrator/add-component)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/add-component"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/add-component/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/jpicklyk/task-orchestrator/add-component"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/add-component.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.00081 | $0.00900 |
| Opus 5.5 | $0.00032 | $0.00360 |
| Sonnet 5.5 | $0.00016 | $0.00180 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
add-component 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 20d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding New Components
Moved from the root CLAUDE.md so it loads only when needed. The single-source documentation policy summary stays in CLAUDE.md; this file is the full procedure.
New MCP Tool
- Extend
BaseToolDefinitionincurrent/src/main/kotlin/.../application/tools/ - Register in
buildMcpTools()(CurrentMcpServer.kt) —ToolDocumentationConsistencyTestandToolTokenBudgetTestderive their tool list from this function, so registering here is sufficient for both guard tests to pick up the new tool automatically - Update all three documentation surfaces (see below)
- Add a
ToolTokenBudgetTestper-tool ceiling row for the new tool (see that test's "BUDGET PHILOSOPHY" doc comment for how to measure and set it) — its sync check fails loudly if a row is missing - Add tests in
current/src/test/kotlin/io/github/jpicklyk/mcptask/current/application/tools/
Tool Documentation Surfaces — Single-Source Policy (post token-efficiency program)
Every tool has three documentation surfaces:
| Surface | Location | Audience |
|---|---|---|
description string |
In the tool source file | LLMs — seen via tools/list |
parameterSchema |
In the tool source file | MCP clients — drives validation |
| API reference | current/docs/api-reference.md |
Humans |
Single source of truth per parameter: each parameter is documented ONCE, in its own
parameterSchema field description — not duplicated in the tool's prose description string.
The prose description is reserved for what a flat JSON Schema cannot express: operation/mode
enum selection, mode-selection rules, trigger effects (e.g. the trigger table in advance_item),
gate semantics, and mutual-exclusion/XOR constraints across fields. This keeps the tools/list
payload lean — the MCP Token-Efficiency Program cut the full tool payload substantially by removing
exactly this kind of prose/schema duplication; ToolTokenBudgetTest guards the result going
forward with per-tool ceilings rather than a single aggregate number.
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.
- 20d ago Changed · +5 lines 9cf34e47c059
- 29d ago First seen · 55 lines · 81 tokens per session scan A b5a05b342691
add-component is a skill published in the GitHub repository jpicklyk/task-orchestrator (208 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 900 once invoked, about $0.0003 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-09-17.
Other skills, from other repositories
performance-caching-rate-limits
Use this capability for performance optimization, load tests, k6/JMeter/Locust plans, caching, Redis, CDN, Cache-Control, invalidation, rate limiting, quotas, token bucket, sliding window, 429 behavior, abuse protection, and cost-based throttling.
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
database-patterns
Database design and migration patterns for Alembic migrations, schema design (SQL/NoSQL), and database versioning. Use when creating migrations, designing schemas, normalizing data, managing database versions, or handling schema drift.
data-contract-migrations
Design and verify data contracts, schema changes, migrations, rollbacks, backfills, compatibility windows, tenant isolation, and API-to-database field mapping. Use when changing database schema, event payloads, persisted documents, analytics tables, multi-tenant data boundaries, or any user-visible data contract where…
generic-fullstack-feature-developer
Guide feature development for full-stack applications with architecture focus. Covers Next.js App Router patterns, NestJS backend services, database models, data workflows, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.
multitenant
Architecture multitenant avec approche tiered (Shared/Dedicated Schema/DB), RBAC/ABAC, field-level encryption. Use when working with multitenant applications, tenant isolation, data segregation.