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 RaNDoM6913/claude-code-superkit --skill project-scannergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/project-scanner)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/project-scanner"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/project-scanner/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/random6913/claude-code-superkit/project-scanner"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/project-scanner.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.00023 | $0.01626 |
| Opus 5.5 | $0.00009 | $0.00650 |
| Sonnet 5.5 | $0.00005 | $0.00325 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
project-scanner 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Scanner
Static reference for project introspection: file markers, import signals, and bash snippets that identify a repo's languages, frameworks, database, infrastructure, structure, components, and scale. Read the tables and apply them to the project in front of you — this file holds no per-project data.
Use when
- You need to identify an unfamiliar project's stack, structure, or scale from its files alone.
- Building a project summary (languages, frameworks, DB, infra, components, auth, CI/CD) before deeper work.
Do not use when
- The project is already described in
CLAUDE.md/AGENTS.md— read that first; only re-detect what it omits. - You already know the one fact you need from a file you have read (e.g. framework stated in
package.json).
Hard Rules
- Detect from files actually present — read or grep the marker; never infer a stack from the project's name.
- Report EVERY detected language, not just the first — polyglot repos are common.
- Multiple structure matches → choose the most specific (see Tie-breaks) and name the signals that fired.
- No marker matches a category → report
UNKNOWNfor it. Never guess a value.
Scan procedure
- Languages — match file markers (Languages table); read each hit's version source. Report all matches.
- Frameworks — for each detected language, grep dependencies against the Frameworks table.
- Database & infrastructure — check docker-compose,
.env, and schema files (Database + Infrastructure tables). - Structure — classify the repo against the Structure Patterns table, applying Tie-breaks.
- Components — scan top-level and second-level directories (Component Detection table).
- Scale — run the Scale Estimation snippets for approximate counts.
Done when: every category above has a concrete value or UNKNOWN.
Detection Patterns
Languages
| File Marker | Language | Version Source |
|---|---|---|
go.mod |
Go | First line: go X.Y |
package.json + tsconfig.json |
TypeScript | package.json → typescript version |
package.json (no tsconfig) |
JavaScript | package.json → engines.node |
pyproject.toml |
Python | [project] → requires-python |
requirements.txt |
Python | None (check python --version) |
Cargo.toml |
Rust | [package] → edition |
pom.xml |
Java | <java.version> |
build.gradle / build.gradle.kts |
Kotlin/Java | sourceCompatibility |
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.
- 1mo ago First seen · 133 lines · 23 tokens per session scan A d52dd615d993
project-scanner is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 1,626 once invoked, about $0.0001 per session on Opus 5.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
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
Honesty Check
Run the volunteering ledger before declaring work done. Forces surfacing of what changed/didn't, what was noticed-but-not-fixed, what was guessed, and what tradeoffs were made on the principal's behalf. The standard - the principal should never be surprised later by something the agent knew at the time.
Envelope
Classify any incoming directive as Ship / Ask one focused question / Propose first. Forces a sharp decision instead of a multi-option survey to the principal. The default failure mode for agents is treating ship-work as ask-work (over-surveying) or treating propose-work as ship-work (rushing irreversible changes).…
nightly-ledger-capture
Discovers missing honesty, trust-decay, failure-mode, and decision-outcome entries from local evidence; stages judgment and permits direct mutation only after an executable oracle.
reconcile
Read-only attention reconciliation. Computes actual seven-day project attention from daily notes against explicit Tier-1 intended shares.
sweep-tracker
Hestia's delegation tracker sweep skill. Reads DELEGATIONTRACKER.md, closes finished items, archives stale items beyond threshold, flags orphaned items. Returns counts. Edit-only on status fields.