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-status)<a href="https://agentmods.dev/commands/skenetechnologies/skene/skene-status"><img src="https://agentmods.dev/badge/commands/skenetechnologies/skene/skene-status/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/commands/skenetechnologies/skene/skene-status"><img src="https://agentmods.dev/badge/commands/skenetechnologies/skene/skene-status.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.00046 | $0.00163 |
| Opus 5.5 | $0.00018 | $0.00065 |
| Sonnet 5.5 | $0.00009 | $0.00033 |
| Haiku 4.5 | $0.00005 | $0.00016 |
Grade A, and why
skene-status 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
Check Implementation Status
- Invoke the
validate-loopskill. - Run
uvx skene status --helpfirst to discover available flags. - Run autonomously. Present the CLI engine status table. No mid-flow questions.
- Explain the Detail column: for action features, "Found in" lists the newest matching migration basename;
(+N)means N other migration files also contain that trigger. - Highlight gaps, suggest next step (
/skene-buildor/skene-deploy).
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 · 13 lines · 46 tokens per session scan A ba8b7815b978
skene-status is a command published in the GitHub repository SkeneTechnologies/skene (126 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 163 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 commands, from other repositories
usage
Show Claude plan usage windows (5h session, 7d all models, per-model weekly like Fable/Opus/Sonnet, extra-usage credits).
dashboard
Open the claudetop web dashboard showing spending charts and session history.
export
Export Claude Code session history as CSV or JSON.
pricing
Update Claude model pricing to latest rates.
branch
Show Claude Code costs per git branch / PR.
stats
Show Claude Code spending analytics (today/week/month/all/tag/branch).