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 The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill hofstadters-lawgit clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/hofstadters-law)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/hofstadters-law"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/hofstadters-law/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/hofstadters-law"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/hofstadters-law.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.00098 | $0.00854 |
| Opus 5.5 | $0.00039 | $0.00342 |
| Sonnet 5.5 | $0.00020 | $0.00171 |
| Haiku 4.5 | $0.00010 | $0.00085 |
Grade A, and why
hofstadters-law 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hofstadter's Law
"It always takes longer than you expect, even when you take into account Hofstadter's Law." — Douglas Hofstadter, 1979 (Gödel, Escher, Bach)
The core idea
Software projects almost always take longer than estimated — and this isn't just because people are bad at estimating. The law's self-referential structure is the point: even when you know about the tendency to underestimate, you will still underestimate. The bias is deeper than awareness alone can fix.
Why this happens
1. Optimism bias. Humans naturally plan for the best-case scenario, not the median. We imagine things going right.
2. Unknown unknowns. You can estimate the work you can see. You can't estimate the work you don't know exists yet — and software always has more of that than expected.
3. Complexity is non-linear. Adding features to an existing system is slower than adding them to a greenfield one. Each new piece interacts with everything already there.
4. Integration and testing always take longer than the coding. Developers estimate the coding time, then implicitly assume everything else is "not much." It's always much.
5. Interruptions and context switching. Calendar time is not development time. Meetings, incidents, code reviews, and dependencies eat calendar days without appearing in estimates.
6. The planning fallacy. People plan based on how similar past projects went (not well) while estimating based on an idealized version of the current project.
Practical responses
Estimation strategies:
- Double your gut estimate. Not rigorous, but often closer to right.
- Use historical data. How long did similar things actually take? Use that as your baseline, not your intuition.
- Three-point estimation. Ask: best case, worst case, most likely case. Combine them: (Best + 4×Most Likely + Worst) / 6. This builds in some uncertainty.
- Break work into small pieces. Estimates are more accurate for small tasks than large ones. A "1-month project" is harder to estimate accurately than 20 "1-week tasks."
- Add explicit buffer for integration. When estimating a feature, separately estimate: coding, testing, integration, code review, deployment, monitoring. The non-coding parts are often 40–60% of the total.
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 · 59 lines · 98 tokens per session scan A 57910393111b
hofstadters-law is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 854 once invoked, about $0.0004 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
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
outcome-tracker
Record the testable predictions inside a decision, then score them against reality later — so frameworks earn trust from outcomes, not vibes. Use when committing to a prioritisation, forecast, or plan (to log what it predicts), when asked to review what actually happened, or to compute how well-calibrated past RICE…