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-initgit 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-init)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/team-init"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-init/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-init"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-init.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.00034 | $0.00543 |
| Opus 5.5 | $0.00014 | $0.00217 |
| Sonnet 5.5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
team-init 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 15d 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.
What it actually says
team-init
What this skill does
Reverse-engineer Context Directive Records (CDRs) from an existing
codebase (brownfield) to document reusable patterns for contribution to
team-ai-directives.
Replaces the former team-init skill. Drafts are written to the adlc
orphan branch of team-ai-directives (not project-local .adlc/drafts/).
When to use
- Brownfield projects: Existing code without team-wide directives
- Legacy modernization: Extract reusable patterns before refactoring
- Team onboarding: Turn implicit conventions into explicit directives
When NOT to use
- Greenfield (session complete): Use
/team-levelupto extract from session - Mining git history: Use
/change-initfor past decisions
Process
Phase 0: Environment Setup
Run: scripts/team-init.sh --setup
Resolves REPO_ROOT, TEAM_AI_DIRECTIVES, NEXT_CDR, ADLC_BRANCH.
Phase 1: Sub-System Detection
Analyze codebase for distinct sub-systems (same detection as former team-init):
src/auth/→ Authenticationservices/payment/→ Payment- etc.
Phase 2: Load Team Directives
Read existing team-ai-directives main branch for comparison (avoid duplicates).
Phase 3: Multi-Agent Analysis
- Discovery Agent: Scan each sub-system for raw patterns
- Pattern Agent: Classify and score patterns for reusability
- Synthesis Agent: Cross-sub-system analysis and CDR generation
Phase 4: Write CDRs
Write to adlc branch drafts/cdr/ using the shared CDR draft template at skills/team/templates/cdr-draft-template.md.
Phase 5: Handoff
Suggest running /team-levelup to review and publish the discovered CDRs.
Verification
- CDRs written to
adlcbranchdrafts/cdr/ - No CDRs in
.adlc/drafts/(old location) -
cdr.mdindex regenerated inadlcbranch
What ships with it
1 file 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.
- 15d ago Changed f1b7f0d16b51
- 24d ago First seen · 70 lines · 34 tokens per session scan A 5a84fa1fcb60
team-init is a skill published in the GitHub repository tikalk/adlc-team-skills (141 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 543 once invoked, about $0.0001 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-22.
Other skills, from other repositories
batch-all-issues
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the goal-pr skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
post-issue-comment
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
ticket-craft
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing.
create-scrap-issue
Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.