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/pyck-ai/pyck-oss/agents-mdgit clone --depth 1 https://github.com/pyck-ai/pyck-ossWrote 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/pyck-ai/pyck-oss/agents-md)<a href="https://agentmods.dev/instructions/pyck-ai/pyck-oss/agents-md"><img src="https://agentmods.dev/badge/instructions/pyck-ai/pyck-oss/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.01956 | $0.01956 |
| Opus 5 | $0.00978 | $0.00978 |
| Sonnet 5 | $0.00391 | $0.00391 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
pyck-oss 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 today.
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.
- today Changed · +19 tokens per session 36a284dead3d
- 4d ago First seen · 216 lines · 1,937 tokens per session scan A 99a6a21ed195
pyck-oss AGENTS.md is an instructions file published in the GitHub repository pyck-ai/pyck-oss (20 stars, last pushed 3d ago), with no licence file. It adds 1,956 tokens to every session, about $0.0098 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-08-30.
Other instructions, from other repositories
pentagi CLAUDE.md
Claude Code instructions for vxcontrol/pentagi, covering claude.md, core interaction rules, project overview, build & development commands and backend (run from backend/).
netdata AGENTS.md
AGENTS.md instructions for netdata/netdata, covering agents.md, goals, requirement language, working with the user and development principles.
telepresence AGENTS.md
Instructions for telepresenceio/telepresence, covering agents.md, project overview, git workflow, design plans and build artifacts.
fulling AGENTS.md
Instructions for FullAgent/fulling, covering agents.md, project overview, tech stack, code conventions and current implementation context.
netdata CLAUDE.md
Claude Code instructions for netdata/netdata, a project described as: The fastest path to AI-powered full stack observability, even for lean teams.
netdata GEMINI.md
Gemini CLI instructions for netdata/netdata, a project described as: The fastest path to AI-powered full stack observability, even for lean teams.