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/docxology/template/rulesnpx skills add docxology/template --skill rulesgit 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/rules)<a href="https://agentmods.dev/skills/docxology/template/rules"><img src="https://agentmods.dev/badge/skills/docxology/template/rules.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.00171 | $0.01289 |
| Opus 5 | $0.00086 | $0.00645 |
| Sonnet 5 | $0.00034 | $0.00258 |
| Haiku 4.5 | $0.00017 | $0.00129 |
Grade A, and why
infrastructure-rules 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 yesterday.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules Module
Discovery, validation, scope, and sidecar symlink sync for the rules/
workspace — soft guidelines (markdown, prompt-style) and strong formal
constraints (yaml/json), distinct from projects/ (executable code) and
fonds/ (data resource pools).
Modules
| File | Exports |
|---|---|
__init__.py |
RuleInfo, build_rule_info, discover_rules, resolve_rule_root, validate_rule_structure |
discovery.py |
discover_rules, resolve_rule_root, NON_RENDERED_RULE_SUBDIRS, RENDERED_RULE_SUBDIRS |
rules_info.py |
RuleInfo, build_rule_info |
validation.py |
validate_rule_structure |
public_scope.py |
PUBLIC_RULE_NAMES, public_rule_infos, public_rule_names |
linking.py |
sync_private_rule_links, sync_active_rule_links, private_rules_root, is_managed_symlink, LIFECYCLE_LINK_DIRS, LinkSyncResult |
Discovery and validation
from pathlib import Path
from infrastructure.rules import discover_rules, resolve_rule_root, validate_rule_structure, RuleInfo
# Discover all valid rules (skips working/, archive/)
rules: list[RuleInfo] = discover_rules(Path("."))
for r in rules:
print(r.qualified_name, r.rule_type, r.is_valid)
# Resolve by name
path = resolve_rule_root(Path("."), "templates/template_project_rules")
path = resolve_rule_root(Path("."), "template_project_rules") # bare name
# Validate structure (requires rules.yaml + soft/ or strong/)
is_valid, message = validate_rule_structure(Path("rules/templates/template_project_rules"))
RuleInfo dataclass
from infrastructure.rules import RuleInfo, build_rule_info
info = build_rule_info(Path("rules/templates/template_project_rules"))
info.name # "template_project_rules"
info.rule_type # "type" from rules.yaml, or "project"
info.has_soft # True iff soft/ exists
info.has_strong # True iff strong/ exists
info.is_valid # True iff has_soft or has_strong
info.qualified_name # "template_project_rules" or "program/name"
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.
- yesterday First seen · 137 lines · 171 tokens per session scan A 5fd54c1777e6
infrastructure-rules is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 171 tokens to every session and 1,289 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
computer-systems-analyst
Use when a task needs the judgment of a Computer Systems Analyst — running requirements elicitation and gap analysis against a target system, writing a feasibility study for a build-vs-buy-vs-customize decision, designing a system integration approach (point-to-point vs middleware vs API-led), scoping data-migration…
construction-trades-supervisor
Use when a task needs the judgment of a Construction Trades Supervisor (foreman) — allocating a crew's daily task assignments against a labor-unit budget, deciding whether today's scope requires a formally designated OSHA competent person, arbitrating a trade-sequencing conflict between crews needing the same physical…
corrections-sergeant
Use when a task needs the judgment of a corrections sergeant or shift supervisor — mandating overtime to restore a post below minimum staffing, reviewing and countersigning a subordinate's use-of-force report, running progressive discipline for a line officer, assuming incident command during a multi-officer response…
architectural-engineering-manager
Use when a task needs the judgment of an Architecture/Engineering firm or department manager — pricing a project fee (lump sum vs. hourly vs. % of construction cost), staffing a project against backlog, evaluating scope creep on a fixed-fee job, managing professional liability exposure, or deciding whether to pursue a…
biomass-power-plant-manager
Use when a task needs the judgment of a Biomass Power Plant Manager — running a biomass-fired power generation facility, managing fuel supply logistics and quality variability, evaluating combustion/efficiency problems, or balancing generation output against fuel cost and emissions constraints.
chief-executive
Use when a task needs the judgment of a CEO/chief executive — setting company strategy, allocating scarce resources (capital, headcount, attention) across competing priorities, making a call that only the top of the org can make, or communicating direction to the board, investors, or the whole company.