Borrowing it
Nothing to install: this file belongs to shyamsridhar123/agentsmith-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shyamsridhar123/agentsmith-cli/main/.github/skills/repo-scanning-and-detection/SKILL.mdgit clone --depth 1 https://github.com/shyamsridhar123/agentsmith-cliWrote 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/shyamsridhar123/agentsmith-cli/repo-scanning-and-detection)<a href="https://agentmods.dev/skills/shyamsridhar123/agentsmith-cli/repo-scanning-and-detection"><img src="https://agentmods.dev/badge/skills/shyamsridhar123/agentsmith-cli/repo-scanning-and-detection/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/shyamsridhar123/agentsmith-cli/repo-scanning-and-detection"><img src="https://agentmods.dev/badge/skills/shyamsridhar123/agentsmith-cli/repo-scanning-and-detection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 24 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
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.00022 | $0.00192 |
| Opus 5 | $0.00011 | $0.00096 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
repo-scanning-and-detection 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 11d 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.
What it actually says
Repo Scanning And Detection
Enumerate files, detect language/framework, and identify config/test/source directories.
When to Use
Use this skill when:
- Working with code in
src/scanner/index.ts/ - User mentions "scan"
- User mentions "glob"
- User mentions "language"
- User mentions "framework"
- User mentions "config"
- User mentions "tests"
Patterns
- glob-based enumeration with ignore filters
- language detection via extension counts and tsconfig override
- framework detection via package.json dependencies
- config and test file heuristics
- source directory inference from common roots
Examples
const scanner = new Scanner(rootPath, verbose); const result = await scanner.scan();
Category
architecture - Structural patterns and system design
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.
- 11d ago First seen · 39 lines · 22 tokens per session scan A d8a716ea5d68
repo-scanning-and-detection is a skill published in the GitHub repository shyamsridhar123/agentsmith-cli (16 stars, last pushed 12d ago), licensed MIT. It adds 22 tokens to every session and 192 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
okteto-debugging
Use when the user describes a broken or unhealthy Okteto environment. Triggers on phrases like: "service is crashing", "service keeps restarting", "service won't start", "environment is broken", "deployment is failing", "pods are stuck", "pods are not ready", "pods are pending", "CrashLoopBackOff", "OOMKilled"…
phoenix-doctor
Diagnose and repair a Phoenix install with the same objective discipline Phoenix gives the agent — check whether the installed agent, skills, and MCP registration match what this build ships, and re-sync any drift with a snapshot-backed fix that is re-verified red→green. Use when Copilot says "No such agent: phoenix"…
phoenix-build
Implement one planned step at a time under the verify-heal loop — snapshot before risky edits, make the smallest change, sense the objective check, and heal (rollback or retry) if it goes red. Never advance to the next step on a red check, never claim a step done without a green sense. Use during implementation, or…
phoenix-debug
Systematic triage and self-healing when something breaks — reproduce with an objective check first, isolate the cause with the code graph, fix the root not the symptom, and confirm with phoenixsense before claiming it resolved. Use when a test/build is red, a regression appears, or the user says /phoenix-debug, "it…
phoenix-self-heal
The core verify-then-heal loop usable on its own for any change with a checkable outcome — sense success objectively, snapshot known-good state, and recover (bounded rollback or retry) when a check goes red, confirmed by an external recheck. Use whenever you make a change that has a runnable test/build/lint, or when…