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.
git 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/commands/skenetechnologies/skene/skene-init)<a href="https://agentmods.dev/commands/skenetechnologies/skene/skene-init"><img src="https://agentmods.dev/badge/commands/skenetechnologies/skene/skene-init.svg" alt="Measured on agentmods" 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.00039 | $0.00179 |
| Opus 5 | $0.00019 | $0.00089 |
| Sonnet 5 | $0.00008 | $0.00036 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
skene-init 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.
What it actually says
Initialize Skene
- Invoke the
initialize-configskill. - Run
uvx skene config --helpfirst to discover available flags. Do not assume flags exist. - Run autonomously. Detect existing config, env vars, user-level config. Fix mismatches, apply defaults. Handle all CLI prompts silently. Only ask the user if API key is missing everywhere.
- If a terminal gets stuck on a prompt, kill it and re-run with piped input.
- End with one line: "Skene init complete. Provider: X, model: Y. Run
/skene-analyzenext."
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 · 13 lines · 39 tokens per session scan A 621db56683de
skene-init is a command published in the GitHub repository SkeneTechnologies/skene (122 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 179 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-08-30.