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 bboyfarouk__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/bboyfarouk__skills)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/bboyfarouk__skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/bboyfarouk__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/bboyfarouk__skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/bboyfarouk__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.00068 | $0.01047 |
| Opus 5 | $0.00034 | $0.00524 |
| Sonnet 5 | $0.00014 | $0.00209 |
| Haiku 4.5 | $0.00007 | $0.00105 |
Grade A, and why
greploop 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 8d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Greploop
Iteratively fix a PR until Greptile gives a perfect review: 5/5 confidence, zero unresolved comments.
Inputs
- PR number (optional): If not provided, detect the PR for the current branch.
Instructions
1. Identify the PR
gh pr view --json number,headRefName -q '{number: .number, branch: .headRefName}'
Switch to the PR branch if not already on it.
2. Loop
Repeat the following cycle. Max 5 iterations to avoid runaway loops.
A. Trigger Greptile review
Push the latest changes (if any) and wait for Greptile's review check to appear:
git push
Then poll for the Greptile check to complete:
gh pr checks <PR_NUMBER> --watch
B. Fetch Greptile review results
Get the latest review from Greptile:
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/reviews
Look for the most recent review from greptile-apps[bot] or greptile-apps-staging[bot].
Parse the review body for:
- Confidence score: Greptile includes a score like
3/5or5/5in its review summary. - Comment count: Number of inline review comments.
Also fetch all unresolved inline comments:
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments
Filter to comments from Greptile that are on the latest commit.
C. Check exit conditions
Stop the loop if any of these are true:
- Confidence score is 5/5 AND there are zero unresolved comments
- Max iterations reached (report current state)
D. Fix actionable comments
For each unresolved Greptile comment:
- Read the file and understand the comment in context.
- Determine if it's actionable (code change needed) or informational.
- If actionable, make the fix.
- If informational or a false positive, note it but still resolve the thread.
E. Resolve threads
Fetch unresolved review threads and resolve all that have been addressed (see GraphQL reference):
gh api graphql -f query='
query($cursor: String) {
repository(owner: "OWNER", name: "REPO") {
pullRequest(number: PR_NUMBER) {
reviewThreads(first: 100, after: $cursor) {
pageInfo { hasNextPage endCursor }
nodes {
id
isResolved
comments(first: 1) {
nodes { body path author { login } }
}
}
}
}
}
}'
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.
- 8d ago First seen · 168 lines · 68 tokens per session scan A 0684e54f5557
greploop is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 1,047 once invoked, about $0.0003 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
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.
review-prs
Triage open PRs — screen from the diff, delegate the admission judgment to audit-the-list, then merge or close on GitHub. Fire when the maintainer asks to review PRs, process the PR queue, or judge whether a specific PR should be merged.
babysit
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
review-open-pull-requests
List and analyze all open pull requests across GitHub repositories. Shows review status, CI/CD check results, age, and reviewers. Use when triaging PRs, checking team velocity, or identifying stale reviews that need attention.
github-review-pr
Review GitHub pull requests with evidence-backed, multi-perspective analysis and false-positive filtering. Use when the user asks to review, inspect, or check a GitHub pull request by number or URL. Default to reporting findings locally; publish comments, submit reviews, or approve only when the user explicitly…
pr-workflow
Prepares branches and PRs for clean, reviewable merges.