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/thetangstr/clockchain-developer-tools/agents-mdgit clone --depth 1 https://github.com/thetangstr/clockchain-developer-toolsWhat 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.00558 | $0.00558 |
| Opus 5 | $0.00279 | $0.00279 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
clockchain-developer-tools AGENTS.md scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Run `npm test` before pushing.** Verifying only via live curl / a running server is The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 39 lines · 558 tokens per session scan A 2de9f691656a
clockchain-developer-tools AGENTS.md is an instructions file published in the GitHub repository thetangstr/clockchain-developer-tools (1 stars, last pushed 19d ago), with no licence file. It adds 558 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
mcp-klever-vm CLAUDE.md
Instructions for klever-io/mcp-klever-vm, covering claude.md, project overview, common commands, architecture and data flow.
attestix CLAUDE.md
Instructions for VibeTensor/attestix: For additional context about technologies to be used, project structure, shell commands, and other important information, read the current plan.
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.