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 instructions/pantheon-org/tekhne/agents-mdgit 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/instructions/pantheon-org/tekhne/agents-md)<a href="https://agentmods.dev/instructions/pantheon-org/tekhne/agents-md"><img src="https://agentmods.dev/badge/instructions/pantheon-org/tekhne/agents-md.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.01609 | $0.01609 |
| Opus 5 | $0.00805 | $0.00805 |
| Sonnet 5 | $0.00322 | $0.00322 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
tekhne AGENTS.md 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tekhne Agent Collaboration Guide
This file defines how LLM agents should work in this repository.
Project Purpose
- Maintain a curated collection of reusable agent skills under
skills/. - Keep skill content modular, discoverable, and easy to lint/validate.
- Prefer small, targeted edits over broad rewrites.
Repository Map
skills/<domain>/<skill-name>/SKILL.md: Primary entry point for a skill.skills/<domain>/<tool>/{generator,validator}/SKILL.md: Generator/validator pairs (consolidated under<tool>/tile.json).skills/<domain>/<skill-name>/AGENTS.md: Optional deep navigation for that skill.skills/<domain>/<skill-name>/references/: Focused reference documents.skills/<domain>/<skill-name>/scripts/: Utility scripts used by a skill.skills/<domain>/<skill-name>/templates/: Reusable templates (mostly YAML).skills/<domain>/<skill-name>/schemas/: JSON schemas for validation..context/: Working notes and generated analysis artifacts.crates/: Rust tools (skill-auditor,skill-validator-rs,adr,journal) for auditing, validation, and skill distribution.scripts/catalog/: TypeScript catalog generator forREADME.mdand the docs tiles page.
Note: Generator/validator pairs are consolidated at the tool level (e.g. terraform-generator and terraform-validator share skills/infrastructure/terraform/tile.json).
Domain Organization
13 domains: ci-cd/, infrastructure/, repository-mgmt/, development/, agentic-harness/, testing/, software-engineering/, observability/, documentation/, package-mgmt/, project-mgmt/, specialized/, languages/.
See skills/agentic-harness/skill-quality-auditor/references/skill-taxonomy.md for classification criteria.
Required Workflow For Agents
- Read the relevant
SKILL.mdbefore editing files in that skill. - Load only the minimum additional files needed for the task.
- Reuse existing templates/scripts instead of recreating content.
- Keep changes scoped to the user request; do not refactor unrelated skills.
- Run validation commands before finishing.
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 · 129 lines · 1,609 tokens per session scan A 32509031837c
tekhne AGENTS.md is an instructions file published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed 3d ago), licensed MIT. It adds 1,609 tokens to every session, about $0.0080 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-31.
Other instructions, from other repositories
superpowers-reasonix AGENTS.md
Instructions for christopherarter/superpowers-reasonix, covering project guidance, skills — stop. load a skill before you act, red flags — these thoughts mean stop. you are rationalizing and priority.
ai-mind AGENTS.md
AGENTS.md instructions for HWYD/ai-mind, covering agents, version spec workspace continuity (mandatory), 项目定位, 事实来源优先级 and 开始大改前先读什么.
vvvv-skills CLAUDE.md
Claude Code instructions for tebjan/vvvv-skills, covering vvvv gamma, when to patch vs code, core concepts, live environment and important conventions.
pi AGENTS.md
AGENTS.md instructions for counterposition/pi, covering agents.md, commands, pattern: pnpm --filter @counterposition/pi-web-search run, single test file and single test by name.
hyperskills CLAUDE.md
Instructions for hyperb1iss/hyperskills, a project described as: My collection of agent skills for a variety of tasks.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).