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 change-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/change-init)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/change-init"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/change-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/change-init"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/change-init.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 Excessive Agency · line 270 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00040 | $0.03637 |
| Opus 5.5 | $0.00016 | $0.01455 |
| Sonnet 5.5 | $0.00008 | $0.00727 |
| Haiku 4.5 | $0.00004 | $0.00364 |
Grade A, and why
change-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 25d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
change-init
What this skill does
Mine git history for Change Decision Records (ChDRs) — the why behind how the code came to be — and write them as draft records for human review.
A ChDR captures a decision that was made in the past and survives only in commits + linked issue trackers:
- Scan a window of
git logfor commit messages that reference an issue tracker (JIRA keys, GitHub/GitLab#NNN, MR!NNN, or issue URLs) - Cluster commits sharing one issue key into a single change story
- Best-effort fetch the issue title/body (GitLab via MCP, GitHub via
gh, else link-only) for requirement-level context - Infer the Decision from the diff summary; record Consequences (reverts, follow-up fix chains — the negative knowledge almost never documented elsewhere)
- Write
ChDR-{NNN}.mdto{REPO_ROOT}/.adlc/drafts/chdr/with status Discovered - Regenerate
{REPO_ROOT}/.adlc/drafts/chdr/chdr.mdindex
Key differences from the team-levelup family:
| Skill | Source | Record | Question answered |
|---|---|---|---|
/team-init |
current code (what IS) | CDR (Context Directive) | what patterns are reusable |
/team-levelup |
current session | CDR | what was learned this session |
/change-init (this skill) |
git history (why it BECAME) | ChDR (Change Decision) | why this code exists / what was tried and reverted |
ChDRs are project-local memory (this repo's evolution), not team-wide context — they fail the team-levelup "team-wide applicability" signal gate. They publish to {REPO_ROOT}/docs/adlc/memory/chdr/ (see /change-publish), and their index is injected at session start by team-boot.
When to use
Note: Routine decision capture is handled by team-boot's continuous capture mechanism, which writes lightweight drafts directly to
.adlc/drafts/. This skill is for interactive deep-dive exploration — when you want guided trade-off analysis, multi-option comparison, or structured decision facilitation before documenting.
What ships with it
2 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.
- 25d ago Changed be22adb04b56
- 1mo ago Changed · +6 lines · +3 tokens per session b8afc154740e
- 1mo ago Changed · -35 tokens per session 2d6e66b7a790
- 1mo ago First seen · 321 lines · 72 tokens per session scan A d23f3972b3bb
change-init is a skill published in the GitHub repository tikalk/adlc-team-skills (143 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 3,637 once invoked, about $0.0002 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-30.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
prs-awaiting-author
List open pull requests where the ball is in the author's court: CI is failing, review comments are unaddressed, or a maintainer question is awaiting the author's reply. Use when the user wants to see PRs awaiting author action.
prs-awaiting-maintainer
List open pull requests where the ball is in the maintainer's court: CI is green and the PR is ready for a maintainer to review, re-review, or merge. Use when the user wants to see PRs awaiting maintainer action.
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.
commit-push-pr
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.