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 standards-reviewgit 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/standards-review)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/standards-review"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/standards-review/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/standards-review"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/standards-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 90 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00060 | $0.01570 |
| Opus 5 | $0.00030 | $0.00785 |
| Sonnet 5 | $0.00012 | $0.00314 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
standards-review 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standards Review
Review a set of project standards through a structured, one-at-a-time interview. Each standard is presented individually with actionable options; the user picks one and moves on. Ends with a confirmed recap and a written report.
Mindset
Every standard should be clear, enforceable, and necessary. If it's not all three, it needs work.
The interview is a triage loop — for each standard, present it, get the user's action, and move on. Do not over-analyse a single standard or extend the interview beyond the user's stated scope.
When to Use
- A team has codified standards (in
RULES.md,CONTRIBUTING.md, or similar) and wants to audit them - Onboarding to a new project and reviewing whether existing standards still apply
- Before a migration or refactor, checking which standards are still relevant
- After a period of drift, to clean up stale or contradictory standards
- The user explicitly asks for a "standards review" or to "audit our rules"
Prerequisites
- The standards file must exist at a path the agent can read.
- The file must have parseable structure (Markdown headings, numbered lists, or line-separated entries).
Workflow
1. Get the file path
Ask the user for the path to their standards file. Use a single question tool call with the file path as the only question.
Expected file formats, in priority order:
| Format | Parsing rule |
|---|---|
Markdown (*.md) |
Each ## / ### / #### heading block is one standard. If no headings exist, each bullet list item (- / *) is one standard. |
| Plain text | Each non-empty line is one standard. |
Read the file with the Read tool. Parse it into individual standard entries.
If the file has no detectable structure, ask the user how standards are delimited before continuing.
2. Confirm scope
Tell the user how many standards were found and ask if they want to review all of them. If the count is 0, report that no standards were detected and offer to re-parse with a user-specified delimiter.
What ships with it
26 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.
- evals/instructions.json 2.4 KB
- evals/scenario-01/capability.txt 175 B
- evals/scenario-01/criteria.json 1.5 KB
- evals/scenario-01/task.md 2.1 KB
- evals/scenario-02/capability.txt 153 B
- evals/scenario-02/criteria.json 1.0 KB
- evals/scenario-02/task.md 1.8 KB
- evals/scenario-03/capability.txt 127 B
- evals/scenario-03/criteria.json 886 B
- evals/scenario-03/task.md 1.6 KB
- evals/scenario-04/capability.txt 129 B
- evals/scenario-04/criteria.json 698 B
- evals/scenario-04/task.md 1.2 KB
- evals/scenario-05/capability.txt 127 B
- evals/scenario-05/criteria.json 715 B
- evals/scenario-05/task.md 1.4 KB
- evals/scenario-06/capability.txt 126 B
- evals/scenario-06/criteria.json 696 B
- evals/scenario-06/task.md 1.1 KB
- evals/scenario-07/capability.txt 141 B
- evals/scenario-07/criteria.json 649 B
- evals/scenario-07/task.md 1.2 KB
- evals/scenario-08/capability.txt 141 B
- evals/scenario-08/criteria.json 677 B
- evals/scenario-08/task.md 988 B
- evals/summary.json 158 B
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 · 148 lines · 60 tokens per session scan A 3a850ffb5086
standards-review is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 1,570 once invoked, about $0.0003 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.