What is template-agentic-use?

A workflow for finding and routing project work to relevant agent skills. It is designed for a research-project template and covers documentation, skill coverage, manifests, and external skill evaluation.

Use it to discover skills, improve agent navigation, audit prompts and documentation, check editor and operations manifests, and evaluate whether an external skill should be installed.

Agents can miss useful instructions when a repository has many skills and configuration files. The workflow helps identify the right guidance and check whether the project exposes it consistently.

template-agentic-use — Skill by docxology

Install

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.

agentmods

npx agentmods add skills/docxology/template/agentic-use

Any agent

npx skills add docxology/template --skill agentic-use

Clone the repo

git clone --depth 1 https://github.com/docxology/template

Made for: Claude Code, Codex.

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,328 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00092	$0.02328
Opus 5	$0.00046	$0.01164
Sonnet 5	$0.00018	$0.00466
Haiku 4.5	$0.00009	$0.00233

Measured 2d ago against content hash 68d5fede31f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

template-agentic-use 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 2d 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.

docs/prompts/agentic-use/SKILL.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agentic use

Natural invoke

"Discover all relevant skills for working with template/"
"Make this repo easier for agents to navigate"
"Improve skill routing and eval coverage"
"Check whether an external skill should be installed or just referenced"
"Review Steward OS and learn useful skills or ideas for template/"
"Review autoresearch-cli and learn measurement-loop patterns for template/"
"Can LEANN semantic memory help template agents navigate this repo?"
"Install Agent Skills for Context Engineering across Codex, Claude, and Hermes"

Inputs to confirm

Scope - skill discovery only, routing docs, or contract/eval hardening.
External installs - default is no install and no vendoring unless explicitly requested.
Audience - local agents, maintainers, or new contributors.

Workflow

Inventory - run uv run python -m infrastructure.skills list-json, check, check-contracts, operations-check, and runtime-status when user-level parity is in scope. Use docs/_generated/skills_index.md as the human index, .cursor/skill_manifest.json as the editor manifest, and .cursor/operations_manifest.json as the Codex/MCP operation catalog.
Route locally first - choose docs/prompts/SKILL.md (template-workflows) for broad template work, then exactly one child skill for implementation. Use this skill only for agent onboarding, routing, skill-surface maintenance, and external-skill review.
Harden discoverability - update the hub routing table, README, mode registry, trigger eval set, and generated manifest/index when the skill surface changes. Avoid unrelated documentation normalization.
Evaluate external skills - check install count, source reputation, and repository health. Record strong candidates as optional companion skills; do not add external skill directories to this public repo by default.
Adopt external references template-first - when a reference such as Steward OS, AutoResearch CLI, or LEANN is useful, translate the idea into template-native routing, eval, local guide, or deterministic infrastructure language. Do not copy external SKILL.md bodies, add scheduled jobs, create public-write automation, install MCP servers, or vendor external directories unless the user explicitly requests that separate implementation.

Read the full file on GitHub · 151 lines

Files

What ships with it

2 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.

Changes

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.

2d ago First seen · 151 lines · 92 tokens per session scan A 68d5fede31f5

Subscribe to this mod's changes

template-agentic-use is a skill published in the GitHub repository docxology/template (19 stars, last pushed 2d ago), licensed Apache-2.0. It adds 92 tokens to every session and 2,328 once invoked, about $0.0005 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.

Building agents LaTeX agents-md ai-agents claude-code computational-research cursor

ai-stance

Generate and maintain AISTANCE.md for any uFawkes repo. Use when onboarding a repo to the uFawkesAI suite, when reviewing AI policy currency, or when a new AI tool is being adopted. Implements DORA AI Capability 1.

paruff/uFawkesAI · 58 tokens

context-engineering

Ensure graphify corpus is current and complete before each agent session. Define minimum AI-accessible documentation per repo. Use at session startup to verify internal context is available to AI tools. Implements DORA AI Capability 3.

paruff/uFawkesAI · 48 tokens

agent-config-setup

Generate AI agent config files for any project — Cursor, Claude Code, Copilot, Windsurf, Cline, AGENTS.md. Use when setting up a new project for AI agents.

ofershap/create-agent-config · 43 tokens

agents-md

Generate and safely maintain an AGENTS.md file (the cross-tool standard for guiding AI coding agents, backed by the Linux Foundation's Agentic AI Foundation and read natively by Codex, Cursor, Copilot, Gemini CLI, Aider, Windsurf, Zed, and more). Use this skill when the user wants to document a repo for AI agents…

eugeniughelbur/agents-md · 174 tokens

agent-observability

Emit and consume telemetry spans for agent invocations, skill loads, findings, and decisions. Use when instrumenting the agent system itself or when analyzing agent behavior patterns.

paruff/uFawkesAI · 38 tokens

agents-generator

Generate a complete, project-specific AGENTS.md compatible with the agents.md standard (60k+ open-source projects). Also generates platform-specific files (.cursorrules, Copilot instructions, GEMINI.md) for detected platforms. Use when setting up AI agent rules, creating project conventions for Claude Code, Cursor…

OJPalenzuela/agents-generator · 180 tokens