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/craigk5n/gtimer/agents-mdgit clone --depth 1 https://github.com/craigk5n/gtimerWrote 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/instructions/craigk5n/gtimer/agents-md)<a href="https://agentmods.dev/instructions/craigk5n/gtimer/agents-md"><img src="https://agentmods.dev/badge/instructions/craigk5n/gtimer/agents-md.svg" alt="Measured on agentmods" 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 | $0.01782 | $0.01782 |
| Opus 5 | $0.00891 | $0.00891 |
| Sonnet 5 | $0.00356 | $0.00356 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
gtimer AGENTS.md 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 2d 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.
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.
- 2d ago First seen · 253 lines · 1,782 tokens per session scan A 9bb73f457596
gtimer AGENTS.md is an instructions file published in the GitHub repository craigk5n/gtimer (15 stars, last pushed 2mo ago), with no licence file. It adds 1,782 tokens to every session, about $0.0089 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-02.
Other instructions, from other repositories
lotti AGENTS.md
AGENTS.md instructions for matthiasn/lotti, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
lotti CLAUDE.md
Claude Code instructions for matthiasn/lotti, a project described as: A private logbook with a staff of personal AI assistants. Agents read what you record and propose what to do next — you approve the changes. End-to-end encrypted sync between your own devices — servers only ever see ciphertext. Local AI optional.
logicPOS AGENTS.md
AGENTS.md instructions for logicpulse/logicPOS, covering ai agent instructions — logicpos, what this codebase is, rules of engagement, where to look and testing.
unisic CLAUDE.md
Claude Code instructions for unisic/unisic, covering claude.md, build & run, non-negotiables, what unisic is and planning workflow.
unisic AGENTS.md
AGENTS.md instructions for unisic/unisic, covering agents.md, 1. what unisic is (and is not), non-negotiable product constraints, 2. prime directives and 3. build, run, and dependencies.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).