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 howgit 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/how)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/how"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/how/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/how"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/how.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00115 | $0.03454 |
| Opus 5 | $0.00057 | $0.01727 |
| Sonnet 5 | $0.00023 | $0.00691 |
| Haiku 4.5 | $0.00012 | $0.00345 |
Grade A, and why
how 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 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.
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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How
Ported from the
howskill in cursor/plugins pstack — Cursor, a separate AI-coding-editor product, not to be confused with a text/DB cursor — for use with this harness'sAgenttool. Agent-spawning mechanics below use this repo's actual subagent types (Explore,general-purpose) and Claude model/effort params (sonnet/opus/haiku/fable,low/medium/high/xhigh/max) in place of the original's model names specific to that other editor, and itsreadonlyflag.One more adaptation, not cosmetic: the original has every explorer/synthesizer/critic use Glob/Grep/Read directly. If your environment has a code-graph MCP (e.g.
tokensave,code-review-graph), prefer its structural query tools (tokensave_contextand friends) over raw file search — they return relevant source directly and track symbols across renames, which Glob/Grep/Read cannot do. Every codebase-reading step below names the code-graph tool first and Glob/Grep/Read as the fallback when no such tool is connected. If your code-graph tool supports a per-worktree index, re-index the current worktree before relying on it — a stale index can silently omit symbols only changed there.
Explore the codebase to answer "how does X work?" questions. Produce clear architectural explanations at the level of a senior engineer onboarding onto a subsystem. Enough to build a working mental model, not annotated source code.
Two modes:
- Explain (default). Explore the codebase and produce a clear explanation
- Critique. Explain first, then spawn multiple independent reviewers to identify architectural issues
Prerequisites
- A question scoped to this codebase, not a general architecture question with nothing to explore
- For critique mode specifically: the explanation from Explain mode already produced, since critique never runs standalone
- No code-graph MCP is required — Glob/Grep/Read work, a code-graph tool (e.g.
tokensave) is just cheaper when one is connected
What ships with it
24 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-08-22/Analysis.md 479 B
- .audits/2026-08-22/audit.json 542 B
- .audits/2026-08-22/Remediation.md 1.4 KB
- evals/instructions.json 2.8 KB
- evals/scenario-01/capability.txt 150 B
- evals/scenario-01/criteria.json 1.4 KB
- evals/scenario-01/task.md 1.9 KB
- evals/scenario-02/capability.txt 156 B
- evals/scenario-02/criteria.json 1.4 KB
- evals/scenario-02/task.md 1.9 KB
- evals/scenario-03/capability.txt 136 B
- evals/scenario-03/criteria.json 1.3 KB
- evals/scenario-03/task.md 2.1 KB
- evals/scenario-04/capability.txt 130 B
- evals/scenario-04/criteria.json 812 B
- evals/scenario-04/task.md 2.2 KB
- evals/scenario-05/capability.txt 144 B
- evals/scenario-05/criteria.json 752 B
- evals/scenario-05/task.md 1.9 KB
- evals/summary.json 249 B
- references/critic-prompt.md 2.4 KB
- references/critique-rubric.md 2.8 KB
- references/explainer-prompt.md 3.2 KB
- references/explorer-prompt.md 3.6 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 · 232 lines · 115 tokens per session scan A bffc8ef94abc
how is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 115 tokens to every session and 3,454 once invoked, about $0.0006 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
atlas-obscura
Search Atlas Obscura for weird, wonderful, and hidden gem places near any destination. Find the interesting stuff, not boring plaques. Search by coordinates, get full details with descriptions and images.
agent-code-generator
Generates Agent definitions (.md files) based on user intent and standard templates.
cf-validate
A validator for 1C configuration source files. It checks the XML structure and the files and objects that make up a 1C business-application configuration.