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 Bilal140202/the-lord-of-the-skills --skill feature-flags-flag-and-release-changegit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-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/bilal140202/the-lord-of-the-skills/feature-flags-flag-and-release-change)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/feature-flags-flag-and-release-change"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/feature-flags-flag-and-release-change/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/bilal140202/the-lord-of-the-skills/feature-flags-flag-and-release-change"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/feature-flags-flag-and-release-change.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.00105 | $0.02374 |
| Opus 5 | $0.00053 | $0.01187 |
| Sonnet 5 | $0.00021 | $0.00475 |
| Haiku 4.5 | $0.00011 | $0.00237 |
Grade A, and why
flag-and-release-change 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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flag & Release a PR Change
You're using a skill that takes a pull request whose change should ship behind a feature flag and drives it end to end: decide it needs a flag, create the guarding flag, wire the new behavior behind it on the PR's branch, and record an automated release so the change ships safely once the PR merges.
The deploy is not the release. The merge ships the control path — the flag is created OFF, so deployment always serves the pre-change behavior. The release is the flag operation the automated rollout performs afterward, governed by the environment's policy. Creating the flag OFF and recording the release are deliberately separate things.
This skill is a portable PR orchestrator. It doesn't own the flag mechanics or the release mechanics — it composes three focused skills and adds the PR workflow (read the diff, work in a clone, push to the branch) plus the plan→implement sequencing:
| Step | Owned by | This skill's role |
|---|---|---|
| Decide whether to flag | should-flag-change (advisory, read-only) |
Act on a "yes"; make the call yourself if it wasn't run |
| Create the flag + wire the code | launchdarkly-flag-create |
Invoke it against the change; don't re-teach flag creation or SDK patterns |
| Record the release | flag-release |
Hand off once the flag exists and the code is pushed; don't re-teach rollout mechanics |
Don't duplicate any composed skill's mechanics here. This skill's only unique content is the PR wrapper (clone, three-dot diff, commit/push to the branch) and the plan→implement flow that stitches the three together.
Automation note. An orchestrating harness (e.g. a PR pipeline) can skip this skill and invoke the three composed skills directly —
should-flag-change→launchdarkly-flag-create→flag-release— driving the git and sequencing itself. This skill is the portable, human-in-the-loop path for a developer working a PR by hand.
You work in two phases — plan, then implement — and you check in with the user in between. Never create or modify anything during the plan phase.
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.
- 6d ago First seen · 96 lines · 105 tokens per session scan A 2ea12329daf0
flag-and-release-change is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 105 tokens to every session and 2,374 once invoked, about $0.0005 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-09-06.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-debrief
Summarises the delta between a tool's latest release and the last summary the user saw. Use when the user asks about what's new, the latest release, release notes, or the changelog of one of the supported tools: Claude Code, OpenCode, llama-swap, or llama.cpp.
clawdbot-release-check
Check for new OpenClaw releases and notify once per new version.