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 dimillian__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/dimillian__skills)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/dimillian__skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/dimillian__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/dimillian__skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/dimillian__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.00075 | $0.01768 |
| Opus 5 | $0.00037 | $0.00884 |
| Sonnet 5 | $0.00015 | $0.00354 |
| Haiku 4.5 | $0.00007 | $0.00177 |
Grade A, and why
project-skill-audit 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 12d 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.
This is a copy
100% identical to project-skill-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Skill Audit
Overview
Audit the project's real recurring workflows before recommending skills. Prefer evidence from memory, rollout summaries, existing skill folders, and current repo conventions over generic brainstorming.
Recommend updates before new skills when an existing project skill is already close to the needed behavior.
Workflow
-
Map the current project surface. Identify the repo root and read the most relevant project guidance first, such as
AGENTS.md,README.md, roadmap/ledger files, and local docs that define workflows or validation expectations. -
Build the memory/session path first. Resolve the memory base as
$CODEX_HOMEwhen set, otherwise default to~/.codex. Use these locations:- memory index:
$CODEX_HOME/memories/MEMORY.mdor~/.codex/memories/MEMORY.md - rollout summaries:
$CODEX_HOME/memories/rollout_summaries/ - raw sessions:
$CODEX_HOME/sessions/or~/.codex/sessions/
- memory index:
-
Read project past sessions in this order. If the runtime prompt already includes a memory summary, start there. Then search
MEMORY.mdfor:- repo name
- repo basename
- current
cwd - important module or file names Open only the 1-3 most relevant rollout summaries first. Fall back to raw session JSONL only when the summaries are missing the exact evidence you need.
-
Scan existing project-local skills before suggesting anything new. Check these locations relative to the current repo root:
.agents/skills.codex/skillsskillsRead bothSKILL.mdandagents/openai.yamlwhen present.
-
Compare project-local skills against recurring work. Look for repeated patterns in past sessions:
- repeated validation sequences
- repeated failure shields
- recurring ownership boundaries
- repeated root-cause categories
- workflows that repeatedly require the same repo-specific context If the pattern appears repeatedly and is not already well captured, it is a candidate skill.
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.
- 12d ago First seen · 183 lines · 75 tokens per session scan A c51007657970
project-skill-audit is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 75 tokens to every session and 1,768 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to project-skill-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
serpsmith
Publish SEO articles reliably across AI-agent runtimes.
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
performing-threat-hunting-with-yara-rules
Use YARA pattern-matching rules to hunt for malware, suspicious files, and indicators of compromise across filesystems and memory dumps. Covers rule authoring, yara-python scanning, and integration with threat intel feeds.
hunt-idor
Hunting skill for idor vulnerabilities. Built from 26 public bug bounty reports. Use when hunting idor on any target.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
testrail
Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".