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 docxology/template --skill toolsgit clone --depth 1 https://github.com/docxology/templateWrote 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/docxology/template/tools)<a href="https://agentmods.dev/skills/docxology/template/tools"><img src="https://agentmods.dev/badge/skills/docxology/template/tools/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/docxology/template/tools"><img src="https://agentmods.dev/badge/skills/docxology/template/tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00168 | $0.01158 |
| Opus 5.5 | $0.00067 | $0.00463 |
| Sonnet 5.5 | $0.00034 | $0.00232 |
| Haiku 4.5 | $0.00017 | $0.00116 |
Grade A, and why
infrastructure-tools 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 10d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tools Module
Discovery, validation, scope, and sidecar symlink sync for the tools/
workspace — executable entry points (scripts, skills, agents), distinct from
projects/ (executable research code) and fonds/ (passive data stores).
Modules
| File | Exports |
|---|---|
__init__.py |
ToolInfo, build_tool_info, discover_tools, resolve_tool_root, validate_tool_structure |
discovery.py |
discover_tools, resolve_tool_root, NON_RENDERED_TOOL_SUBDIRS, RENDERED_TOOL_SUBDIRS |
tools_info.py |
ToolInfo, build_tool_info |
validation.py |
validate_tool_structure |
public_scope.py |
PUBLIC_TOOL_NAMES, public_tool_infos, public_tool_names |
linking.py |
sync_private_tool_links, private_tools_root, is_managed_symlink, LIFECYCLE_LINK_DIRS, LinkSyncResult |
Discovery and validation
from pathlib import Path
from infrastructure.tools import discover_tools, resolve_tool_root, validate_tool_structure, ToolInfo
# Discover all valid tools (skips working/, archive/)
tools: list[ToolInfo] = discover_tools(Path("."))
for t in tools:
print(t.qualified_name, t.tool_type, t.is_valid)
# Resolve by name
path = resolve_tool_root(Path("."), "templates/template_code_executor")
path = resolve_tool_root(Path("."), "template_code_executor") # bare name
# Validate structure (requires tools.yaml + scripts/)
is_valid, message = validate_tool_structure(Path("tools/templates/template_code_executor"))
ToolInfo dataclass
from infrastructure.tools import ToolInfo, build_tool_info
info = build_tool_info(Path("tools/templates/template_code_executor"))
info.name # "template_code_executor"
info.tool_type # "type" from tools.yaml, or "generic"
info.has_scripts # True iff scripts/ exists
info.is_valid # True iff has_scripts
info.qualified_name # "template_code_executor" or "program/name"
Public scope
from infrastructure.tools.public_scope import (
PUBLIC_TOOL_NAMES, # ('templates/template_code_executor',)
public_tool_infos, # list[ToolInfo] present in checkout
public_tool_names, # list[str] sorted
)
What ships with it
8 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.
- 10d ago Changed ca15a9f3841d
- 1mo ago First seen · 124 lines · 168 tokens per session scan A 18ffa1773554
infrastructure-tools is a skill published in the GitHub repository docxology/template (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 168 tokens to every session and 1,158 once invoked, about $0.0007 per session on Opus 5.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-09-03.
Other skills, from other repositories
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
concierge
Use when a task needs the judgment of a Concierge — securing a reservation at a fully-booked restaurant or sold-out venue, coordinating a multi-vendor guest request (dinner, transportation, and a gift delivery) inside a tight window, deciding when to pivot from a failed Plan A to a same-caliber Plan B, or navigating a…
correspondence-clerk
Use when a task needs the judgment of a Correspondence Clerk — selecting and customizing a template response to a standardized written inquiry, triaging a correspondence queue against SLA deadlines, deciding when a form letter suffices versus needs escalation, or auditing a response-template library for staleness.
ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering…
open-loops
A conversation-audit skill for finding unresolved points in a long chat. It checks whether questions, suggestions, decisions, or needed clarifications were left without a clear response.
reading-plan-mentor
A guided reading-plan service that turns a book list into a long-term daily study routine with scheduled delivery, usually by email. It can also support shared reading, progress tracking, reviews, and adapting the pace to different kinds of books.