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/mihai-dinculescu/tapo/pre-commitnpx skills add mihai-dinculescu/tapo --skill pre-commitgit clone --depth 1 https://github.com/mihai-dinculescu/tapoWrote 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/mihai-dinculescu/tapo/pre-commit)<a href="https://agentmods.dev/skills/mihai-dinculescu/tapo/pre-commit"><img src="https://agentmods.dev/badge/skills/mihai-dinculescu/tapo/pre-commit.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 | $0.00020 | $0.00982 |
| Opus 5 | $0.00010 | $0.00491 |
| Sonnet 5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
pre-commit 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Commit
Run all checks, fix any issues found, then present a summary table.
Checks
Rust checks
Run the following checks if there are changes in the tapo/, tapo-py/, or tapo-mcp/ directories. Fix all issues found. Run independent checks (cargo check, cargo clippy, cargo fmt, cargo test) in parallel.
Unless otherwise specified, run checks at the workspace level (no -p flags) with --all-features to ensure cross-crate issues are caught.
Link-free checks (check, clippy) take --workspace so they cover tapo-py too; cargo test must NOT — it links test binaries and examples, which fails with tapo-py's pyo3/extension-module, so it relies on default-members excluding tapo-py.
cargo check --workspace --all-featurescargo clippy --workspace --all-featurescargo fmt --allcargo test --all-featurescargo clean --doc && RUSTDOCFLAGS="-D warnings" cargo doc -p tapo --no-deps --all-features- No
unwrap()in non-test code without a// safe:comment - No
unsafein non-test code without a// SAFETY:comment - No unnecessary clones
- No deeply nested
use(max one level of{}nesting)
Python checks
Run the following checks if there are changes in the tapo/ or tapo-py/ directories. Fix all issues found.
- Update
.pyistubs if Python-exposed Rust types changed - Verify new
#[pyclass]types are imported and registered intapo-py/src/lib.rs - Verify Python examples in
tapo-py/examples/are updated to match corresponding Rust examples intapo/examples/ cd tapo-pyand activate the virtual environmentuv run mypy .— fix all type errorsuv run black .— fix all formatting issues
MCP checks
Run the following checks if there are changes in the tapo-mcp/ directory. Fix all issues found.
- Verify that all
#[derive(JsonSchema)]types haveschemarsannotations — including tool input params, response types, enums, and their fields/variants. Check for descriptions and range constraints where applicable. - Verify that
tapo-mcp/README.mdreflects any MCP API changes (tools, resources, capabilities, env vars, auth) - Verify that the OpenClaw skill reflects any MCP API changes. The skill spans three files — check each:
tapo-mcp/openclaw-skill/SKILL.md— frontmatter (description,version,requires), Setup, Tools section with examplenpx mcporter callinvocationstapo-mcp/openclaw-skill/references/setup.md— verification table (tool, description, parameters)tapo-mcp/openclaw-skill/references/tapo-mcp-setup.md— Tools table, Resources table, Configuration env vars, Authentication, Deployment (kept in sync withtapo-mcp/README.md)
- When device-support categories change (e.g. adding a new family like the H100 hub), verify the device-type enumeration is in sync across both surfaces that list it:
tapo-mcp/src/server.rswith_instructions(...)(e.g."plugs, lights, power strips, hubs and their child sensors, cameras")tapo-mcp/openclaw-skill/SKILL.mdfrontmatterdescription:(e.g.(lights, plugs, power strips, hubs and sensors, cameras))
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.
- 4d ago First seen · 63 lines · 20 tokens per session scan A b51604cf0aff
pre-commit is a skill published in the GitHub repository mihai-dinculescu/tapo (798 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 982 once invoked, about $0.0001 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
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…
trellis-finish-work
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
et-git
ET git workflow for preparing commits and reviewing changes. Use when checking git status or diff, filtering unrelated files, staging task-scoped changes, writing Chinese commit messages, or synchronizing with remotes using rebase instead of merge.
commit
Smart commit: bump version, find related issues, commit with Co-authored-by, push. Use when the user says 'commit' or wants to finalize changes.