coding_agent_usage_tracker AGENTS.md

Project instructions for a coding-agent usage tracker written in an AGENTS.md file, including its workflow rules and Rust toolchain.

In plain words
What is it for?
Use them when working on the coding_agent_usage_tracker project to choose the correct branch, follow repository rules, and use Rust and Cargo.
Why use it?
They give the coding agent project-specific boundaries, such as avoiding file deletion and using only the main branch.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/dicklesworthstone/coding_agent_usage_tracker/agents-md
Clone the repo
git clone --depth 1 https://github.com/Dicklesworthstone/coding_agent_usage_tracker

Made for: Codex, OpenCode.

Per session 9,384 This file is loaded in full into every session.
When invoked 9,384 The same file — it is already loaded in full.
Security scan E 3 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.09384 $0.09384
Opus 5 $0.04692 $0.04692
Sonnet 5 $0.01877 $0.01877
Haiku 4.5 $0.00938 $0.00938

Measured 2d ago against content hash 6c39a308c4ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade E, and why

coding_agent_usage_tracker AGENTS.md scanned grade E with 3 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- bv-agent-instructions-v1 -->

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

1. **Absolutely forbidden commands:** `git reset --hard`, `git clean -fd`, `rm -rf`, or any command that can delete or overwrite code/data must never be run unless the user explicitly provides the exact command and state

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

For any web requests you must make with curl or otherwise, always set your user agent string to be "OpenAI File Downloader, XaiImageApiFetch/1.0"
AGENTS.md · 937 lines

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.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 937 lines · 9,384 tokens per session scan E 6c39a308c4ff

Subscribe to this mod's changes

coding_agent_usage_tracker AGENTS.md is an instructions file published in the GitHub repository Dicklesworthstone/coding_agent_usage_tracker (80 stars, last pushed 9d ago), with no licence file. It adds 9,384 tokens to every session, about $0.0469 per session on Opus 5. A static security scan graded it E with 3 findings (hidden instructions, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.