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 tikalk/adlc-team-skills --skill team-skillsgit clone --depth 1 https://github.com/tikalk/adlc-team-skillsWrote 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/tikalk/adlc-team-skills/team-skills)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/team-skills"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-skills/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/tikalk/adlc-team-skills/team-skills"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 132 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00046 | $0.01769 |
| Opus 5 | $0.00023 | $0.00885 |
| Sonnet 5 | $0.00009 | $0.00354 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade A, and why
team-skills 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team-skills
Overview
Browse available skills from the team AI directives and install
selected ones to the current agent's skills directory. Use --all to
install every default and external skill in one pass. Skills are
installed under their original names (no prefix) so they stay in sync
with the manifest.
When to Use
- When the user asks to browse, list, or install team skills.
- When the input names a specific skill to install.
- When extending the agent's capabilities with team-shared skills.
- When
team-setupdelegates/team-skills --allafter initial configuration.
$ARGUMENTS
Core Process
Setup
Read the file .adlc/init-options.json directly. Do NOT use glob, find,
or any file-search tool to locate it — search tools may silently skip
dotfile-prefixed path segments. Read the file at the exact relative path
.adlc/init-options.json from the current working directory.
If that read fails (file not found), walk up parent directories by reading
../.adlc/init-options.json, then ../../.adlc/init-options.json,
and so on — up to 4 levels. Stop at the first successful read.
From the JSON, extract the team_ai_directives field:
{
"team_ai_directives": "/path/to/team-ai-directives"
}
If team_ai_directives is not set, STOP:
Team AI directives not configured.
Run: /team-setup
Helper scripts (relative to skill directory):
$(dirname "$0")/team-helpers.sh --json$(Split-Path $PSCommandPath -Parent)/team-helpers.ps1 -Json
Step 1: Read Skills Manifest
Read {REPO_ROOT}/.skills.json (where {REPO_ROOT} denotes the project
root — the directory where .adlc/ lives) and {TEAM_AI_DIRECTIVES}/.skills.json
(team directives manifest). Merge both, with project-root entries taking
precedence. Parse the manifest sections (schema v2.0.0):
| Section | Description | Installed by --all? |
|---|---|---|
default |
Local skills (in skills/{name}/) auto-installed during setup |
Yes |
external |
Remote skills fetched by URL, installed on demand | Yes |
blocked |
Rejected — must never be installed | Never |
What ships with it
4 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.
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 · 183 lines · 46 tokens per session scan A 755aea94d900
team-skills is a skill published in the GitHub repository tikalk/adlc-team-skills (133 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,769 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-30.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…