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/monkilabs/opencastle/team-lead-referencenpx skills add monkilabs/opencastle --skill team-lead-referencegit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/team-lead-reference)<a href="https://agentmods.dev/skills/monkilabs/opencastle/team-lead-reference"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/team-lead-reference.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.01451 |
| Opus 5 | $0.00032 | $0.00726 |
| Sonnet 5 | $0.00013 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
team-lead-reference 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 yesterday.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Lead Reference
Delegation Sequence
- Score task complexity (table below) → determines tier
- Route to model tier via Cost-Aware Routing
- Deepen plan if 3+ subtasks (Deepen-Plan Protocol)
- Check pre-delegation policy (5-point checklist below)
- Delegate using Compact Delegation Envelope
- Handle output per Status Handling table
- Log via observability-logging skill
For specialist agent registry, model assignments, see .opencastle/agents/agent-registry.md.
Cost-Aware Model Routing
| Tier | Use For |
|---|---|
| Premium | Team Lead orchestration, highest-stakes decisions |
| Quality | Feature implementation, UI/frontend, security, architecture, complex reasoning |
| Standard | Large-scale analysis, schema design, cost-efficient coding, repo exploration |
| Fast | Terminal-heavy tasks, E2E tests, data pipelines, agentic workflows |
| Economy | Docs, simple config, formatting, boilerplate |
Selection: Default to the agent's registry tier. Never Premium/Quality for boilerplate. 3+ parallel agents → prefer Economy/Fast/Standard. Per-task overrides below.
Complexity-Based Task Scoring
| Factor | Low → High |
|---|---|
| Files touched | 1–2 → 3–5 → 6+ / cross-library |
| Reasoning depth | Boilerplate → pattern matching → architecture/security/tradeoffs |
| Ambiguity | Clear spec → some judgment → multiple valid approaches |
| Risk | Reversible → moderate impact → DB/auth/breaking |
| Dependencies | None → 1–2 upstream → complex chain |
| Score | Tier | Examples |
|---|---|---|
| 1–2 | Economy/Fast | Docs update, config tweak, rename, simple test |
| 3–5 | Standard/Quality | Component, CMS query, API route, migration |
| 8 | Quality | Architecture decision, security audit, complex refactor |
| 13 | Quality + Panel | DB migration with data transform, auth flow redesign |
Overrides: Blocker (blocking 2+ downstream) → upgrade one tier. Security-touching or architecture ambiguity → Quality+. Pure docs/config → Economy. Registry default takes precedence unless complexity clearly warrants change.
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.
- yesterday First seen · 127 lines · 64 tokens per session scan A 0d1e1873e614
team-lead-reference is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 1,451 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-09-03.
Other skills, from other repositories
jira-ticket-builder
Turns rough input into structured Jira work. Two modes — single-ticket mode turns a bug description, meeting notes, Slack thread, incident writeup, or a few sentences into one fully-structured Jira ticket; decomposition mode turns a rough requirements doc or product brief with multiple asks and open questions into…
task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation.
find-code-tasks
Lists all code tasks in the repository with their status, dates, and metadata. Useful for getting an overview of pending work or finding specific tasks.
linear
Read Linear issues, transition state, and post comments. The entry point for ticket-driven agent workflows.
product-architect
Complete product development system with 80 agents and 36 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
tsk-add
Queue a single task based on the current conversation using tsk add.