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 monty-python-esquegit 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/monty-python-esque)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/monty-python-esque"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/monty-python-esque/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/monty-python-esque"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/monty-python-esque.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00197 | $0.02119 |
| Opus 5.5 | $0.00079 | $0.00848 |
| Sonnet 5.5 | $0.00039 | $0.00424 |
| Haiku 4.5 | $0.00020 | $0.00212 |
Grade A, and why
monty-python-esque 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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monty Python-esque Comedy
Mindset
The comedy in this tradition is not randomness dressed up as "weird": it is absolute internal consistency applied to an impossible premise. A sketch is funny because the characters treat the absurd with the same procedural seriousness they'd give a tax return, and the escalation follows rules the audience can half-predict a beat before the logic breaks something. If you remember one thing: escalate the logic, don't escalate the randomness.
When to Use
Only use this skill when the request is for new, original material built on an ordinary premise pushed to absurd extremes, not for retrieving or lightly disguising existing content.
- The user asks for an original sketch, script, or short comic bit ("write me a sketch about...", "give me a scene where...", "a bit involving...").
- The premise is ordinary (a council meeting, a customer complaint, a job interview, a queue), and the user wants it pushed to absurd extremes through dialogue.
- The user wants dry, escalating, deadpan-toned comedy rather than punchline-driven one-liners.
- The user references Monty Python's style or tradition as a tone descriptor, not as a request to retrieve or adapt specific existing material.
When NOT to Use
- The user asks for the actual text of an existing Monty Python sketch, or a "rewrite"/"parody" of one that keeps its characters, structure, or catchphrases recognisable. If the user wants to reuse recognisable characters or catchphrases, do not attempt a lightly disguised version; offer new, premise-driven material inspired by the same mechanism instead (see Anti-Patterns).
- The user wants slapstick, physical-comedy description, observational stand-up material, roast jokes, or punchline-per-line sitcom banter: those rely on delivery and timing, not on escalating premise logic, and this skill's techniques will not fit the brief.
- The user wants comedy about a real, named, identifiable person in a way that could read as mockery of them specifically rather than of the absurd situation.
What ships with it
25 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 481 B
- .audits/2026-08-22/audit.json 544 B
- .audits/2026-08-22/Remediation.md 1.0 KB
- .audits/2026-10-02/Analysis.md 481 B
- .audits/2026-10-02/audit.json 544 B
- .audits/2026-10-02/Remediation.md 1.2 KB
- evals/instructions.json 2.3 KB
- evals/scenario-01/capability.txt 215 B
- evals/scenario-01/criteria.json 1.4 KB
- evals/scenario-01/task.md 2.1 KB
- evals/scenario-02/capability.txt 177 B
- evals/scenario-02/criteria.json 1.5 KB
- evals/scenario-02/task.md 1.9 KB
- evals/scenario-03/capability.txt 193 B
- evals/scenario-03/criteria.json 1.4 KB
- evals/scenario-03/task.md 2.2 KB
- evals/scenario-04/capability.txt 117 B
- evals/scenario-04/criteria.json 572 B
- evals/scenario-04/task.md 1.2 KB
- evals/scenario-05/capability.txt 114 B
- evals/scenario-05/criteria.json 725 B
- evals/scenario-05/task.md 1.6 KB
- evals/summary.json 68 B
- references/deadpan-delivery-and-abrupt-endings.md 5.1 KB
- references/escalation-and-bureaucratic-engines.md 6.2 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.
- 1mo ago First seen · 175 lines · 197 tokens per session scan A 80f8c6be4d9a
monty-python-esque is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed today), licensed MIT. It adds 197 tokens to every session and 2,119 once invoked, about $0.0008 per session on Opus 5.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 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…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
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 generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.