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 skills add pantheon-org/tekhne --skill managing-chezmoi-packagesgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/managing-chezmoi-packages)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/managing-chezmoi-packages"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/managing-chezmoi-packages/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/pantheon-org/tekhne/managing-chezmoi-packages"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/managing-chezmoi-packages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 352 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00088 | $0.03483 |
| Opus 5 | $0.00044 | $0.01741 |
| Sonnet 5 | $0.00018 | $0.00697 |
| Haiku 4.5 | $0.00009 | $0.00348 |
Grade A, and why
managing-chezmoi-packages 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://github.com/USER/REPO/raw/SHA/path/to/file How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Chezmoi Packages
This skill handles all aspects of package and dependency management in chezmoi dotfiles repositories, with emphasis on security, reproducibility, and automated updates.
Core Principles
- Version Pinning: Always pin to immutable references (commit SHAs, specific versions, digests)
- Renovate Automation: Ensure all dependencies have corresponding Renovate rules
- Organization: Group externals by primary program using
.chezmoiexternals/directory - Minimal Edits: Make focused changes without unrelated modifications
- Preview First: Show proposed changes before applying
When to Use This Skill
Invoke this skill when the user requests:
- Adding/updating/removing packages or tools
- Managing chezmoi external dependencies
- Pinning versions or updating SHAs
- Organizing external files by program
- Setting up Renovate automation for dependencies
- Choosing between package ecosystems (Homebrew, mise, etc.)
Workflow
1. Identify the Request
Determine what the user wants:
- Add: New package or external dependency
- Update: Change version/SHA of existing package
- Remove: Delete package or external
- Organize: Migrate externals to
.chezmoiexternals/structure - Pin: Add immutable version/SHA reference
2. Select the Ecosystem
Choose the appropriate package manager (see ./ecosystem-guide.md for details):
| Use Case | Ecosystem | Location |
|---|---|---|
| macOS packages (Homebrew) | brew/cask/mas | home/.chezmoidata/packages.yaml |
| CLI developer tools | mise (Aqua) | .mise.toml or home/dot_config/mise/config.toml |
| Python tools | pip | home/dot_config/dotfiles/requirements.txt |
| Docker/devcontainer | docker | home/dot_config/docker-compose/*.yml, .devcontainer/ |
| External files/repos | chezmoi externals | home/.chezmoiexternals/*.toml[.tmpl] |
| Install script CLIs | cli-versions | home/dot_config/dotfiles/cli-versions.toml |
What ships with it
25 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.
- .audits/2026-04-24/analysis.md 1.2 KB
- .audits/2026-04-24/audit.json 506 B
- .audits/2026-04-24/remediation-plan.md 3.0 KB
- .audits/latest 10 B
- evals/instructions.json 7.8 KB
- evals/scenario-0/capability.txt 62 B
- evals/scenario-0/criteria.json 2.2 KB
- evals/scenario-0/task.md 1.2 KB
- evals/scenario-1/capability.txt 58 B
- evals/scenario-1/criteria.json 2.0 KB
- evals/scenario-1/task.md 1.3 KB
- evals/scenario-2/capability.txt 55 B
- evals/scenario-2/criteria.json 2.1 KB
- evals/scenario-2/task.md 1.3 KB
- evals/scenario-3/capability.txt 48 B
- evals/scenario-3/criteria.json 2.3 KB
- evals/scenario-3/task.md 1.9 KB
- evals/scenario-4/capability.txt 70 B
- evals/scenario-4/criteria.json 2.4 KB
- evals/scenario-4/task.md 2.6 KB
- evals/summary_infeasible.json 58 B
- evals/summary.json 253 B
- references/ecosystem-guide.md 8.6 KB
- references/externals-reference.md 7.2 KB
- references/renovate-integration.md 7.9 KB
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.
- 9d ago First seen · 406 lines · 88 tokens per session scan A bd7fe2128345
managing-chezmoi-packages is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 3,483 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
stay-within-limits
Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
agent-estate
Perpetual autonomous work loop for Claude Code — no end condition, no memory regression, no context overfill. Maintains a persistent ledger across all sessions.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…