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 agentmods add skills/skenetechnologies/skene/initialize-confignpx skills add SkeneTechnologies/skene --skill initialize-configgit 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/initialize-config)<a href="https://agentmods.dev/skills/skenetechnologies/skene/initialize-config"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/initialize-config.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.00051 | $0.00803 |
| Opus 5 | $0.00026 | $0.00402 |
| Sonnet 5 | $0.00010 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade C, and why
initialize-config scanned grade C with 1 finding 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 6d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
- `printenv SKENE_API_KEY SKENE_PROVIDER 2>/dev/null` — env vars How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Skene Configuration
Set up Skene automatically. The user runs /skene-init, everything gets configured, and they see a one-line summary. Zero questions unless something is genuinely missing and cannot be inferred.
Config reference: Configuration guide.
Design principle
Make init invisible. Detect everything from existing config, env vars, and user-level config. Only ask the user if the agent truly cannot figure it out (e.g. API key missing everywhere).
Steps
-
Discover CLI options Run
uvx skene config --helpto see what flags are available. Use only flags that appear in the output. -
Check what already exists (run in parallel where possible):
ls .skene.config 2>/dev/null— project configls ~/.config/skene/config 2>/dev/null— user-level configecho n | uvx skene config --show— full resolved config (piped to avoid blocking)printenv SKENE_API_KEY SKENE_PROVIDER 2>/dev/null— env vars
-
Decide what to do (no user interaction needed):
Case A — Config exists and is valid (provider set, API key present, provider/model match): Done. Report summary.
Case B — Config exists but has issues (provider/model mismatch, missing API key, etc.): Fix what you can automatically:
- Provider/model mismatch → update
.skene.configwith correct defaults. - API key missing from file but
SKENE_API_KEYin env → fine, note it. - API key missing everywhere → ask user: "Set
SKENE_API_KEYin your environment, then re-run/skene-init."
Case C — No config at all:
- Run
uvx skene config --init(check --help first to confirm this flag exists). - If that fails with permission error, write
.skene.configTOML directly. - Infer provider from env vars or default to
openai. - Validate with
echo n | uvx skene config --show.
- Provider/model mismatch → update
-
Final validation
echo n | uvx skene config --showConfirm provider, model, API key. If good, report.
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.
- 6d ago First seen · 71 lines · 51 tokens per session scan C 9bbc9c37516c
initialize-config is a skill published in the GitHub repository SkeneTechnologies/skene (122 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 803 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
omh-code-review
This is a Hermes-native code-review workflow skill.