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 nbsp1221__agent-skillsgit 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/nbsp1221__agent-skills)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/nbsp1221__agent-skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/nbsp1221__agent-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/bilal140202/the-lord-of-the-skills/nbsp1221__agent-skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/nbsp1221__agent-skills.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.00049 | $0.01251 |
| Opus 5 | $0.00024 | $0.00626 |
| Sonnet 5 | $0.00010 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
commit 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 9d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Follow the repo's existing convention, create the commit, verify, and push when requested. Use the reference docs for detailed rules.
Workflow
-
Identify the convention
- Read agent guidance first:
AGENTS.md,CLAUDE.md, etc. - Check repo guidance or templates if present:
CONTRIBUTING.md,README.md, commit templates, etc. - Scan history:
git log -n 50 --pretty=%s - Choose exactly one: Conventional Commits, Gitmoji, or Custom.
- If ambiguous, pause and ask using the user input guidance below.
- Never invent new commit types or emoji codes.
- Read agent guidance first:
-
Pull if requested
- If
--pullis set, rungit pullbefore reviewing changes. - If conflicts occur, try to resolve them. If you cannot, pause and ask using the user input guidance below.
- If
-
Review changes
git status -sbgit diff --statgit diff(orgit diff --staged)- Split unrelated changes into separate commits.
-
Stage intentionally
- Prefer
git add -porgit add <files> - Do not stage secrets or large generated artifacts unless explicitly requested.
- Prefer
-
Run verify steps
- If the repo has tests, lint, or format checks, run them before committing.
- Only proceed if they pass, unless the user requests
--no-verify. - If checks fail, try to resolve them. If you cannot, pause and ask using the user input guidance below.
-
Compose the message
- If a convention is identified, you MUST open the matching reference and follow its rules before composing the message.
- Conventional Commits: follow
references/conventional-commits.md. - Gitmoji: follow
references/gitmoji.md. - Custom template: follow the exact pattern from history or the template file.
- Use a body and trailers when needed (blank line before body, wrap at 72 chars).
-
Commit, inspect, and push
- ALWAYS run the commit through the guard script (do not use
git commitdirectly):- Resolve
{baseDir}(the installed skill root) before running:- Check project-scoped installs first:
./.claude/skills/commit,./.codex/skills/commit,./.opencode/skills/commit - Then check user-scoped installs:
~/.claude/skills/commit,~/.codex/skills/commit,~/.opencode/skills/commit
- Check project-scoped installs first:
- Use
{baseDir}/scripts/commit-guard.py:python {baseDir}/scripts/commit-guard.py --convention <conventional|gitmoji|custom> --message "subject"python {baseDir}/scripts/commit-guard.py --convention <conventional|gitmoji|custom> --file <path>
- If
{baseDir}cannot be found, pause and ask the user for the exact skill install path.
- Resolve
git log -1 --format="%h %s"git show --stat- If
--pushis set, push to the current branch after commit. - If push fails, pause and ask using the user input guidance below.
- ALWAYS run the commit through the guard script (do not use
What ships with it
3 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.
- 9d ago First seen · 106 lines · 49 tokens per session scan A 4435f793eb90
commit is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 1,251 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-09-03.
Other skills, from other repositories
git-pushing
Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes ("push this", "commit and push"), mentions saving work to remote ("save to github", "push to remote"), or completes a feature and wants to share it.
git-commit-formatter
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
conventional-commits
Writes git commit messages following the Conventional Commits 1.0.0 spec. Use when committing changes, when the user asks for a commit message, or when a repo enforces commit linting.
agy-implementer
Delegate a coding task to Google's Antigravity CLI (agy staffer, fast Gemini), which edits the working tree directly and can perform explicitly requested Git delivery. Use when the user says /skill:agy-implementer, "have agy fix/build X", or wants to hand a well-scoped coding task to the agy staffer instead of doing…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
git-pr-workflows-git-workflow
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g.