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/d4rkninja/infynon-cli/agents-mdgit clone --depth 1 https://github.com/d4rkNinja/infynon-cliWrote 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/d4rkninja/infynon-cli/agents-md)<a href="https://agentmods.dev/instructions/d4rkninja/infynon-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/d4rkninja/infynon-cli/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.00297 | $0.00297 |
| Opus 5 | $0.00148 | $0.00148 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
infynon-cli 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 4d 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.
What it actually says
AGENTS
Release Tag Guardrails
Follow this checklist every time you cut a release tag.
- Pick the release version, for example
0.2.0-beta.9.0.9. If the user asks for a minor update on an active release line, keep the chosen minor version (for example0.3.0) and do not bump again to a patch or another new version unless the user explicitly requests a different version. - Update all release metadata files to the same version:
Cargo.toml([package].version)npm/package.json(version)go/internal/installer/installer.go(const version = "...")
- Validate versions before tagging:
python scripts/verify-release-versions.py v<version>
- Commit the version and workflow changes to
main. - Create an annotated tag using the
vprefix:git tag -a v<version> -m "Release v<version>"
- Push branch first, then push the tag:
git push origin maingit push origin v<version>
Why this is required
.github/workflows/release.ymltriggers on tags matchingv*.- The release workflow runs
scripts/verify-release-versions.py. - If Go/Cargo/npm versions are not synced before tagging, release fails.
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.
- 4d ago First seen · 26 lines · 297 tokens per session scan A 26008886d0af
infynon-cli AGENTS.md is an instructions file published in the GitHub repository d4rkNinja/infynon-cli (8 stars, last pushed 3mo ago), licensed MIT. It adds 297 tokens to every session, about $0.0015 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-31.
Other instructions, from other repositories
lid AGENTS.md
Instructions for jszmajda/lid, covering agents.md, repository purpose, structure, plugin architecture (claude code) and other agentic coding tools.
catalyst AGENTS.md
AGENTS.md instructions for coalesce-labs/catalyst, covering agents.md, what this repository is, agent philosophy, build & test and key principles.
catalyst CLAUDE.md
Claude Code instructions for coalesce-labs/catalyst, covering claude code, loading & invocation, orchestration runtime, pull request review (codex) and code understanding (serena mcp).
lid CLAUDE.md
Instructions for jszmajda/lid, a project described as: Linked-Intent Development - a SDD methodology for agentic coding.
Clawness CLAUDE.md
Instructions for fullymiddleaged/Clawness, covering claude.md — working on clawness, what this is, architecture (request flow), key files and design decisions (don't undo without reading these).
pg-aiguide CLAUDE.md
Claude Code instructions for timescale/pg-aiguide, covering tiger docs mcp server - development guidelines, build, test & run commands, code style guidelines and python (ingest/).