Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tikalk/adlc-team-skillsnpx agentmods add skills/tikalk/adlc-team-skills/levelup-publishWrote 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/levelup-publish)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/levelup-publish"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/levelup-publish/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/levelup-publish"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/levelup-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.04977 |
| Opus 5 | $0.00023 | $0.02488 |
| Sonnet 5 | $0.00009 | $0.00995 |
| Haiku 4.5 | $0.00005 | $0.00498 |
Grade A, and why
levelup-publish 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 11d 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 — 611 lines — stays where its author put it; the contents beside it link to each section on GitHub.
levelup-publish
What this skill does
Compile accepted CDRs into actual artifacts in the team-ai-directives team AI directives and create a draft PR.
It is the implementation phase of the CDR lifecycle:
- Validate accepted CDRs against the signal gate
- Detect cross-CDR conflicts before publishing
- Generate context module files (rules, personas, examples, constitution)
- Generate eval goldenset files (
goldset.md+goldset.json) for eval-type CDRs - Generate skill artifacts (
SKILL.md+.skills-entry.json) - Update
.skills.jsonmanifest - Update
CDR.mdindex in team-ai-directives - Create a branch, commit, and open a draft PR
This skill does not run until CDRs have been accepted via /levelup-clarify.
When to use
- After
/levelup-clarify: Accepted CDRs need to be published - Single skill build: Use
--skill <name|CDR-id>to build one skill - Context modules only: Use
--context-onlyto skip skill generation
When NOT to use
- No accepted CDRs: Run
/levelup-clarifyfirst - Uncommitted changes in team-ai-directives: Clean working tree first
- Discovering patterns: Use
/levelup-initor/levelup-specify - Reviewing CDRs: Use
/levelup-clarify
Process
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Examples of User Input:
"--ready"— Create ready PR instead of draft"--skip-skills"— Don't include skill CDRs"--context-only"— Only build context modules"--skill CDR-005"— Build only the skill from CDR-005"CDR-001 CDR-003"— Only implement specific CDRs- Empty input: Implement all accepted CDRs as draft PR
Flags
--ready: Create ready PR instead of draft--skip-skills: Skip skill-type CDRs--context-only: Build only context modules (skip all skills)--skill <name|CDR-id>: Build only one skill from a specific accepted skill CDR
Role & Context
You are acting as a Context Publisher — moving accepted CDRs from local drafts to team-ai-directives.
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.
- 11d ago First seen · 611 lines · 46 tokens per session scan A 75e82b7f6bc5
levelup-publish is a skill published in the GitHub repository tikalk/adlc-team-skills (133 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 4,977 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
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
polyphony
Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
ijfw-commit
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit.
memstack-security-secrets-scanner
Use this skill when the user says 'scan for secrets', 'check for leaked keys', 'secrets scanner', 'hardcoded credentials', 'API key leak', or needs to detect exposed secrets in source code. Do NOT use for dependency vulnerabilities or RLS auditing.
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.