Borrowing it
Nothing to install: this file belongs to weby-homelab/power-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/weby-homelab/power-framework/main/.agents/skills/power/SKILL.mdgit clone --depth 1 https://github.com/weby-homelab/power-frameworkWrote 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/weby-homelab/power-framework/power)<a href="https://agentmods.dev/skills/weby-homelab/power-framework/power"><img src="https://agentmods.dev/badge/skills/weby-homelab/power-framework/power/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/weby-homelab/power-framework/power"><img src="https://agentmods.dev/badge/skills/weby-homelab/power-framework/power.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.00045 | $0.01139 |
| Opus 5 | $0.00023 | $0.00570 |
| Sonnet 5 | $0.00009 | $0.00228 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
power 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 5d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +9 lines 07d85b9d9503
- 9d ago First seen · 58 lines · 45 tokens per session scan A 4698fc74d4a9
power is a skill published in the GitHub repository weby-homelab/power-framework (20 stars, last pushed today), licensed GPL-3.0. It adds 45 tokens to every session and 1,139 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.
Other skills, from other repositories
brain
Health-check the second brain so failures are not silent: is the local search server alive, is the RAG index fresh, is the session-memory ledger filling, did the nightly distillation run. Read-only, with a green/red verdict per component. Triggers: "/brain", "/memory", "is the reindex alive".
llm-wiki-orient
Explain the LLM-Wiki pattern, its raw/wiki/schema architecture, how it differs from RAG, GraphRAG and agent memory, and what ready-made solution families exist. Use when the user asks what LLM-Wiki is, whether it is worth adopting, what OpenWiki/wiki memory means, or how the ecosystem fits together.
llm-wiki-local-first-stack
Design a local-first LLM-Wiki stack. Use when the user wants Markdown, git, Obsidian, ripgrep, local embeddings, qmd-style retrieval, SQLite/FTS/vector indexes, local LLMs, offline operation, or safe sync without cloud lock-in; route retrieval/index layer design to llm-wiki-retrieval-architect.
knowledge-base-interop
Two-layer knowledge architecture — curate in LLM Wiki, search in Astra KB. Covers input classification, source-to-wiki ingestion, wiki-to-KB export (batch + realtime), semantic chunking, SAG extraction, health checks, and multi-format export.
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
adapter-authoring
Build a custom source → raw-intake adapter for Athenaeum. Use when someone wants to feed an external source (an API, an export file, a message feed, a scraper, another tool's output) into an Athenaeum knowledge base, asks "how do I write an adapter / integration for athenaeum", or wants to turn some data source into…