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 skills add YoungLeadersDotTech/young-leaders-tech-marketplace --skill stakeholder-templatesgit clone --depth 1 https://github.com/YoungLeadersDotTech/young-leaders-tech-marketplaceWrote 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/youngleadersdottech/young-leaders-tech-marketplace/stakeholder-templates)<a href="https://agentmods.dev/skills/youngleadersdottech/young-leaders-tech-marketplace/stakeholder-templates"><img src="https://agentmods.dev/badge/skills/youngleadersdottech/young-leaders-tech-marketplace/stakeholder-templates/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/youngleadersdottech/young-leaders-tech-marketplace/stakeholder-templates"><img src="https://agentmods.dev/badge/skills/youngleadersdottech/young-leaders-tech-marketplace/stakeholder-templates.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.00043 | $0.01361 |
| Opus 5 | $0.00022 | $0.00681 |
| Sonnet 5 | $0.00009 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
stakeholder-templates 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 12d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Justification: pure template scaffold - emits verbatim template content with no LLM reasoning pass.
Stakeholder Discovery Template
Purpose
This template guides the creation of project-specific stakeholder skills. Replace all [PLACEHOLDER] values with actual project information.
SKILL.md Frontmatter Template
---
name: [project]-[domain]-stakeholders
description: Stakeholder context for [PROJECT_NAME] [DOMAIN] when discussing [USE_CASE_1], [USE_CASE_2], or [USE_CASE_3]. Auto-invoke when user mentions [PROJECT_TRIGGER], [DOMAIN_TRIGGER], or [TEAM_TRIGGER]. Do NOT load for general [DOMAIN] discussions unrelated to [PROJECT_NAME].
disable-model-invocation: true
allowed-tools: []
version: 1.0.0
category: Stakeholders
tags: [[project], [domain], [key-theme-1], [key-theme-2]]
last-updated: [YYYY-MM-DD]
---
Description Engineering Guidance:
✅ DO include specific trigger terms:
- Project name (exact capitalization users will mention)
- Domain keywords (fintech, UX research, payment processing)
- Team names users will reference
❌ DON'T use generic descriptions:
- "Provides stakeholder information" (too broad)
- "Use when discussing stakeholders" (will load too often)
- No explicit project scope (will contaminate other projects)
Example Good Description:
Stakeholder context for Apollo UX research project when discussing user testing, research synthesis, or design validation. Auto-invoke when user mentions Apollo, UX research stakeholders, or design team collaboration. Do NOT load for general UX discussions unrelated to Apollo.
Skill Content Structure Template
[TEAM_NAME] Team
Team Objectives
[PRIMARY_OBJECTIVE_1](quantified if possible: >95% accuracy, <100ms latency)[PRIMARY_OBJECTIVE_2][PRIMARY_OBJECTIVE_3]
Key Stakeholders
[ROLE_TITLE] (Use role, not individual name - NO PII)
- Decision Authority:
[SPECIFIC_DECISIONS_THIS_ROLE_MAKES] - Communication Preference:
[PREFERRED_CHANNELS_AND_STYLE]- Examples: "Data-driven with A/B test results", "Formal written proposals", "Technical RFCs with diagrams"
- Success Metrics:
[QUANTIFIABLE_METRICS_THIS_ROLE_CARES_ABOUT]- Format: "[Metric name] [operator][value]" (e.g., "Fraud detection rate >95%")
- Pain Points:
[CURRENT_CHALLENGE_1](quantified if possible)[CURRENT_CHALLENGE_2][CURRENT_CHALLENGE_3]
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.
- 12d ago First seen · 142 lines · 43 tokens per session scan A 566942d70df1
stakeholder-templates is a skill published in the GitHub repository YoungLeadersDotTech/young-leaders-tech-marketplace (10 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,361 once invoked, about $0.0002 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
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.
agentsop-code-execution-decision
Decision rubric for when an LM agent should write-and-run code (Program-of-Thought / code interpreter) versus reason in natural language: classify each step as deterministic- computable (emit + execute code, feed the result back) vs judgment (stay in prose). Use when designing or debugging an agent step that does…
agentsop-dify
SOP for building LLM applications on Dify — visual workflow + chatflow + agent + RAG knowledge base + plugin marketplace + observability, self-hostable. Use when shipping LLM apps fast with a "no-code to pro-code" gradient, especially when non-engineers need to co-author the flow.
agentsop-llamaindex
Operating-system distillation of LlamaIndex — the leading RAG / document-agent framework. Activate when the calling agent must build, debug, harden, or evaluate a Retrieval-Augmented Generation pipeline over unstructured/private data, decide between RAG primitives (Index types, retrievers, query engines, routers…
agentsop-llm-artifact-versioning
Enhancement overlay — version the WHOLE deployable LLM-app artifact as one bundle: prompts + compiled programs + model snapshot pins + retrieval config + eval-set version, versioned together so a deploy is reproducible and rollback is atomic. Activate when preparing to deploy an LLM app, when asking "what exactly is…
agentsop-metric-design
Decomposed, multi-criteria metric design for LLM pipelines. The metric IS the model — change the metric and the optimizer changes behavior. Decompose by default; bool during compile, float during eval; calibrate against human; mitigate judge bias. Search keywords: LLM-as-judge, llm as judge, eval metric, evaluation…