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 SkeneTechnologies/skene --skill analyze-codebasegit clone --depth 1 https://github.com/SkeneTechnologies/skeneWrote 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/skenetechnologies/skene/analyze-codebase)<a href="https://agentmods.dev/skills/skenetechnologies/skene/analyze-codebase"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/analyze-codebase/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/skenetechnologies/skene/analyze-codebase"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/analyze-codebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium MCP Rug Pull · line 22 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 30 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
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.00050 | $0.00467 |
| Opus 5.5 | $0.00020 | $0.00187 |
| Sonnet 5.5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
analyze-codebase 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.
What it actually says
Analyze Codebase
Run the Skene CLI to analyze the codebase. The CLI does the analysis, not you.
Critical rule
Do NOT substitute your own PLG analysis, findings, or guesses if the CLI fails. Run the CLI, present its output on success, report the error on failure. That's it.
Agent behavior rules
- Autonomous. Run the CLI, present results, suggest next step. No mid-flow questions.
- User cannot type into agent terminals. The agent handles all CLI input. Pipe safe defaults for routine prompts. Kill stuck terminals and re-run with piped input.
Steps
-
Discover CLI options Run
uvx skene analyze --helpto see available flags. Use only flags that appear in the output. -
Verify configuration
ls .skene.config 2>/dev/null— if missing: "Run/skene-initfirst." Stop. -
Run analysis Default to project root. Choose appropriate flags based on --help output.
uvx skene analyze .Tell the user: "Running analysis, this may take a few minutes."
-
Handle result
- Success: Read results from
.skene/analysis/,skene-context/, or legacyskene/and present them. Suggest/skene-plan. - Failure: Report the exact error, suggest a fix, stop. Do NOT generate your own analysis.
- Success: Read results from
Error handling
- 429 / quota: "LLM provider quota error. Check billing, then re-run."
- Permission errors: Give user the command to run in their own terminal.
- Timeout: "Try a smaller directory."
- Any other error: Report verbatim.
Output
Success: CLI results + "Run /skene-plan next."
Failure: Error + fix suggestion. No substitute analysis.
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 · 49 lines · 50 tokens per session scan A bdc73671e71c
analyze-codebase is a skill published in the GitHub repository SkeneTechnologies/skene (126 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 467 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
ai-session-search
Search, recover, inspect, export, and analyze local AI session history with AI Session Search (aise) across Claude Code, Claude Desktop local agent, Codex, Cursor, Antigravity, Pi coding agent, Prime Agent, Google AI Studio, and Gemini CLI. Use when asked to "find prior AI work", "recover context after compaction"…
cli2skill
Turn any CLI or MCP server into an Agent Skill. Use when you want to replace an MCP server with a zero-overhead CLI skill, or generate a skill from any command-line tool's --help output.
burnd-analyze-spend
Analyze your OpenClaw API spend — total cost, cost last 7 days, top cost leaks by model and provider, and concrete steps to reduce your bill. Use when the user asks about their AI spending, costs, budget, or which models are costing the most.
brain-log
Show brain sync and evolution history.
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…
healthcheck
System health monitoring and diagnostics - checks profClaw API, Redis, Docker, disk, memory, and processes with actionable status reports.