What is timing-cli AGENTS.md?

Project instructions for timing-cli that tell a coding agent how to track work with Beads and how to run shell and file commands without interactive prompts. Beads stores issues in a local Dolt database, a database that can sync through a Git remote.

They help agents find, claim, update, and close issues, sync issue data, and safely run copying, moving, or removing commands in timing-cli.

They reduce mistakes caused by using the wrong issue-data source, missing the project's work process, or waiting for confirmation prompts during automated work.

timing-cli AGENTS.md — Instructions file by sussdorff

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/sussdorff/timing-cli/agents-md

Clone the repo

git clone --depth 1 https://github.com/sussdorff/timing-cli

Made for: Codex, OpenCode.

Per session 1,444 This file is loaded in full into every session.

When invoked 1,444 The same file — it is already loaded in full.

Security scan C 1 finding. Scan, not verified.

Origin 64% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.01444	$0.01444
Opus 5	$0.00722	$0.00722
Sonnet 5	$0.00289	$0.00289
Haiku 4.5	$0.00144	$0.00144

Measured yesterday against content hash 3f2a55f040ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

timing-cli AGENTS.md scanned grade C 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.

Recursive force deletehighDestructive command

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

rm -rf directory # NOT: rm -r directory

Origin

This is a copy

64% identical to dspy-skills AGENTS.md — 123 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd prime for full workflow context.

Architecture in one line: Issues live in a local Dolt database (.beads/dolt/); cross-machine sync uses bd dolt push/pull (a git-compatible protocol), stored under refs/dolt/data on your git remote — separate from refs/heads/* where your code lives. .beads/issues.jsonl is a passive export, not the wire protocol.

See SYNC_CONCEPTS.md for the one-screen overview and anti-patterns (don't treat JSONL as the source of truth; don't bd import during normal operation; don't reach for third-party Dolt hosting before trying the default).

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work atomically
bd close <id>         # Complete work
bd dolt push          # Push beads data to remote

Non-Interactive Shell Commands

ALWAYS use non-interactive flags with file operations to avoid hanging on confirmation prompts.

Shell commands like cp, mv, and rm may be aliased to include -i (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.

Use these forms instead:

# Force overwrite without prompting
cp -f source dest           # NOT: cp source dest
mv -f source dest           # NOT: mv source dest
rm -f file                  # NOT: rm file

# For recursive operations
rm -rf directory            # NOT: rm -r directory
cp -rf source dest          # NOT: cp -r source dest

Other commands that may prompt:

scp - use -o BatchMode=yes for non-interactive
ssh - use -o BatchMode=yes to fail instead of prompting
apt-get - use -y flag
brew - use HOMEBREW_NO_AUTO_UPDATE=1 env var

Beads Issue Tracker

This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.

Read the full file on GitHub · 128 lines

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.

yesterday First seen · 128 lines · 1,444 tokens per session scan C 3f2a55f040ad

Subscribe to this mod's changes

timing-cli AGENTS.md is an instructions file published in the GitHub repository sussdorff/timing-cli (0 stars, last pushed 8d ago), licensed MIT. It adds 1,444 tokens to every session, about $0.0072 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 64% identical to dspy-skills AGENTS.md, differing in 123 lines, and is treated as a copy.

Databases Git and workflow

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

timing-cli AGENTS.md