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/build-implementationnpx skills add SkeneTechnologies/skene --skill build-implementationgit 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/build-implementation)<a href="https://agentmods.dev/skills/skenetechnologies/skene/build-implementation"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/build-implementation.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.00042 | $0.00527 |
| Opus 5 | $0.00021 | $0.00264 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
build-implementation scanned grade A 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.
Asks the agent to reveal its instructionslowSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
The CLI may present a menu (e.g. "Select option [1/2/3/4]"). Always pipe the option that shows the full prompt in the terminal (typically `3` for "Show full prompt"): Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
What it actually says
Build Implementation Prompt
Generate implementation prompts via the Skene CLI. The CLI generates the plan, not you.
Agent behavior rules
- Autonomous. Run the CLI, read the output, execute the implementation. No mid-flow questions.
- CLI is the source of truth. If
uvx skene buildfails, report the error. Do NOT write your own implementation plan as a substitute. - User cannot type into agent terminals. The agent handles all CLI input.
Steps
-
Discover CLI options Run
uvx skene build --helpto see available flags and understand any interactive prompts. -
Verify loop selection
ls .skene/active-loop.json 2>/dev/null || ls skene-context/growth-loops/ 2>/dev/null || ls skene/growth-loops/ 2>/dev/nullIf missing: "Run/skene-planfirst." Stop. -
Generate implementation prompt The CLI may present a menu (e.g. "Select option [1/2/3/4]"). Always pipe the option that shows the full prompt in the terminal (typically
3for "Show full prompt"):echo 3 | uvx skene buildIf the menu options differ from expected, check --help output or the terminal output to pick the "show/print prompt" option.
-
Read the prompt The CLI saves output to
skene-context/growth-loops/(legacyskene/growth-loops/). Read the full implementation prompt from the terminal output or that directory. -
Execute the prompt Start implementing the steps from the CLI-generated prompt directly. Present a brief summary of what will be done, then execute. Break large implementations into logical chunks.
-
Report completion "Implementation complete. Run
/skene-statusto validate."
Error handling
- CLI failure: Report error, suggest fix. Do NOT fabricate implementation plans.
- Stuck on menu prompt: Kill terminal, re-run with piped input.
- Permission errors: Give user the command for their terminal.
Output
Summary of what was implemented + "Run /skene-status to validate."
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 · 50 lines · 42 tokens per session scan A 9d9bf29824df
build-implementation is a skill published in the GitHub repository SkeneTechnologies/skene (122 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 527 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (asks the agent to reveal its instructions). 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.