time-toolkit AGENTS.md

Project-specific instructions for Time Toolkit, a Python command-line tool, connection server, software library, WebSocket client, and read-only web API for Time Messenger and Mattermost-compatible servers.

In plain words
What is it for?
Use them when developing or publishing Time Toolkit, especially for protecting tokens, using synthetic test data, keeping profile details in results, confirming writes, and running the required checks.
Why use it?
They set safety and testing rules for handling messages, accounts, server profiles, credentials, and changes in that project.

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/erstcl/time-toolkit/agents-md
Clone the repo
git clone --depth 1 https://github.com/erstcl/time-toolkit

Made for: Codex, OpenCode.

Per session 162 This file is loaded in full into every session.
When invoked 162 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00162 $0.00162
Opus 5 $0.00081 $0.00081
Sonnet 5 $0.00032 $0.00032
Haiku 4.5 $0.00016 $0.00016

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

Security

Grade A, and why

time-toolkit 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 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.

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.

AGENTS.md · 13 lines

What it actually says

Project instructions

  • Never print, log, commit, or request Time tokens, cookies, passwords, or CSRF values.
  • Never add real Time messages, channel exports, user lists, or downloaded files as fixtures.
  • Use synthetic fixtures in tests.
  • Keep the explicitly selected profile and server in every structured result.
  • Read operations must not change read state.
  • Writes must name a profile explicitly and support preview/confirmation.
  • Apply readonly, approval, and fullauto identically to every profile name.
  • Use only synthetic .test domains and synthetic messages in tests.
  • Run uv sync --no-editable --all-extras, then uv run --no-sync pytest and uv run --no-sync ruff check . before publishing changes.
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. yesterday First seen · 13 lines · 162 tokens per session scan A 84e85af15c4c

Subscribe to this mod's changes

time-toolkit AGENTS.md is an instructions file published in the GitHub repository erstcl/time-toolkit (0 stars, last pushed 22d ago), licensed MIT. It adds 162 tokens to every session, about $0.0008 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.

Related

Other instructions, from other repositories

deepagents AGENTS.md

AGENTS.md instructions for langchain-ai/deepagents, covering global development guidelines for the deep agents monorepo, corridor security analysis, development workflow, suppressing ruff rules and pr conventions.

langchain-ai/deepagents · 2,268 tokens

python-cheatsheet copilot-instructions.md

Copilot instructions for labex-labs/python-cheatsheet, covering python cheatsheet - ai coding assistant instructions, project overview, architecture & key patterns, content structure and routing & layout system.

labex-labs/python-cheatsheet · 1,155 tokens

autoharness AGENTS.md

Instructions for tigerless-labs/autoharness: This repo uses Open Knowledge — collaborative markdown via MCP. .open-knowledge/config.yml (with optional /.open-knowledge/config.yml; CLI/env may override) is the path contract: content.dir is the root for relative paths; content.include lists globs that add markdown…

tigerless-labs/autoharness · 2,201 tokens

cookiecutter-mlops-package AGENTS.md

Instructions for fmind/cookiecutter-mlops-package, covering agents.md, project overview, setup & core commands, definition of done and conventions & idioms.

fmind/cookiecutter-mlops-package · 1,296 tokens

martex-quant CLAUDE.md

Instructions for martex-dev/martex-quant, covering session start — read these first, project instructions, ai trading bot project - master instructions, role and project objective.

martex-dev/martex-quant · 6,161 tokens

ZipAgent AGENTS.md

Instructions for JiayuXu0/ZipAgent, covering repository guidelines, project structure & module organization, build, test & development commands, coding style & naming conventions and testing guidelines.

JiayuXu0/ZipAgent · 504 tokens