Borrowing it
Nothing to install: this file belongs to barateza/mcp-plesk-dev-docs. 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/barateza/mcp-plesk-dev-docs/main/.github/skills/tlc-spec-driven/SKILL.mdgit clone --depth 1 https://github.com/barateza/mcp-plesk-dev-docsWrote 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/barateza/mcp-plesk-dev-docs/tlc-spec-driven)<a href="https://agentmods.dev/skills/barateza/mcp-plesk-dev-docs/tlc-spec-driven"><img src="https://agentmods.dev/badge/skills/barateza/mcp-plesk-dev-docs/tlc-spec-driven/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/barateza/mcp-plesk-dev-docs/tlc-spec-driven"><img src="https://agentmods.dev/badge/skills/barateza/mcp-plesk-dev-docs/tlc-spec-driven.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.00148 | $0.01069 |
| Opus 5.5 | $0.00059 | $0.00428 |
| Sonnet 5.5 | $0.00030 | $0.00214 |
| Haiku 4.5 | $0.00015 | $0.00107 |
Grade A, and why
tlc-spec-driven 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Lead's Club - Spec-Driven Development
Plan and implement projects with precision. Granular tasks. Clear dependencies. Right tools.
┌──────────┐ ┌──────────┐ ┌─────────┐ ┌───────────────────┐
│ SPECIFY │ → │ DESIGN │ → │ TASKS │ → │ IMPLEMENT+VALIDATE│
└──────────┘ └──────────┘ └─────────┘ └───────────────────┘
Project Structure
.specs/
├── project/
│ ├── PROJECT.md # Vision & goals
│ ├── ROADMAP.md # Features & milestones
│ └── STATE.md # Memory between sessions
├── codebase/ # Brownfield analysis (existing projects)
│ ├── STACK.md
│ ├── ARCHITECTURE.md
│ ├── CONVENTIONS.md
│ ├── STRUCTURE.md
│ ├── TESTING.md
│ └── INTEGRATIONS.md
└── features/ # Feature specifications
└── [feature]/
├── spec.md
├── design.md
└── tasks.md
Workflow
New project:
- Initialize project → PROJECT.md
- Create roadmap → ROADMAP.md
- Specify features → existing workflow
Existing codebase:
- Map codebase → 6 brownfield docs
- Initialize project → PROJECT.md + ROADMAP.md
- Specify features → existing workflow
Context Loading Strategy
Base load (~15k tokens):
- PROJECT.md (if exists)
- ROADMAP.md (when planning/working on features)
- STATE.md (persistent memory)
On-demand load:
- Codebase docs (when working in existing project)
- spec.md (when working on specific feature)
- design.md (when implementing from design)
- tasks.md (when executing tasks)
Never load simultaneously:
- Multiple feature specs
- Multiple architecture docs
- Archived documents
Target: <40k tokens total context Reserve: 160k+ tokens for work, reasoning, outputs Monitoring: Display status when >40k (see context-limits.md)
Commands
Project-level:
| Trigger Pattern | Reference |
|---|---|
| Initialize project, setup project | project-init.md |
| Create roadmap, plan features | roadmap.md |
| Map codebase, analyze existing code | brownfield-mapping.md |
| Record decision, log blocker | state-management.md |
| Pause work, end session | session-handoff.md |
| Resume work, continue | session-handoff.md |
What ships with it
15 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.
- .skill-meta.json 121 B
- README.md 15 KB
- references/brownfield-mapping.md 7.9 KB
- references/code-analysis.md 2.2 KB
- references/coding-principles.md 1.3 KB
- references/context-limits.md 1.3 KB
- references/design.md 3.3 KB
- references/implement.md 2.0 KB
- references/project-init.md 1.4 KB
- references/roadmap.md 1.4 KB
- references/session-handoff.md 1.3 KB
- references/specify.md 2.8 KB
- references/state-management.md 2.4 KB
- references/tasks.md 5.8 KB
- references/validate.md 2.9 KB
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 · 115 lines · 148 tokens per session scan A 6a5131cbe8bf
tlc-spec-driven is a skill published in the GitHub repository barateza/mcp-plesk-dev-docs (2 stars, last pushed 2mo ago), licensed MIT. It adds 148 tokens to every session and 1,069 once invoked, about $0.0006 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
fastmcp-client-cli
Query and invoke tools on MCP servers using fastmcp list and fastmcp call. Use when you need to discover what tools a server offers, call tools, or integrate MCP servers into workflows.
code-review
Review code for quality, maintainability, and correctness.
triaging-incidents
Creating, triaging, updating, and analyzing ServiceNow incidents, including trend reports. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM…
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
vault-workflow
Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.