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 onboarding-sdk-install-detectgit 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/onboarding-sdk-install-detect)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/onboarding-sdk-install-detect"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/onboarding-sdk-install-detect/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/onboarding-sdk-install-detect"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/onboarding-sdk-install-detect.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.00040 | $0.03010 |
| Opus 5 | $0.00020 | $0.01505 |
| Sonnet 5 | $0.00008 | $0.00602 |
| Haiku 4.5 | $0.00004 | $0.00301 |
Grade A, and why
detect 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detect repository stack (SDK install)
Before installing anything, you must understand the project. Identify what the project is built with and whether LaunchDarkly is already present.
This skill is nested under LaunchDarkly SDK Install (onboarding); the parent Step 1 is detect. Next: Generate integration plan unless the decision tree sends you elsewhere.
1. Language and framework
Look for the indicator files below (and related root layout), then read the relevant manifests to infer language and framework.
Look for these files to identify the stack:
| File | Language/Framework |
|---|---|
package.json |
JavaScript/TypeScript (check for React, Next.js, Vue, Angular, Express, React Native, Electron, etc.) |
requirements.txt, pyproject.toml, Pipfile, setup.py |
Python (check for Django, Flask, FastAPI) |
go.mod |
Go (check for Gin, Echo, Fiber, Chi) |
pom.xml, build.gradle, build.gradle.kts |
Java/Kotlin (check for Spring, Quarkus, Android) |
Gemfile |
Ruby (check for Rails, Sinatra) |
*.csproj, *.sln, *.fsproj |
.NET/C# (check for ASP.NET, MAUI, Xamarin, WPF, UWP) |
composer.json |
PHP (check for Laravel, Symfony) |
Cargo.toml |
Rust (check for Actix, Axum, Rocket) |
pubspec.yaml |
Flutter/Dart |
Package.swift, Podfile, *.xcodeproj |
Swift/iOS |
AndroidManifest.xml |
Android (also check build.gradle for com.android) |
rebar.config, mix.exs |
Erlang/Elixir |
CMakeLists.txt, Makefile (with C/C++ patterns) |
C/C++ (check for #include patterns) |
*.cabal, stack.yaml |
Haskell |
*.lua, rockspec |
Lua |
manifest, *.brs |
Roku (BrightScript) |
wrangler.toml |
Cloudflare Workers (edge SDK) |
vercel.json with edge functions |
Vercel Edge (edge SDK) |
Read the dependency file to identify the specific framework. For package.json, check both dependencies and devDependencies.
If you cannot identify the language or framework:
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 · 218 lines · 40 tokens per session scan A 6933c492c32e
detect is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 3,010 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-06.
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".