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/apet97/clockify-python/agents-mdgit clone --depth 1 https://github.com/apet97/clockify-pythonWhat 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.02929 | $0.02929 |
| Opus 5 | $0.01465 | $0.01465 |
| Sonnet 5 | $0.00586 | $0.00586 |
| Haiku 4.5 | $0.00293 | $0.00293 |
Grade A, and why
clockify-python 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clockify-python CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository maintenance guide
Purpose
- Maintain the released
clockify-python-115package. - Optimize for users, adopters, contributors, and maintainers.
- Use small direct changes that match the current architecture.
- Prefer evidence from source, tests, artifacts, and live boundaries.
- Do not restart the completed
0.1.0perfection campaign. - Do not add ceremony, speculative helpers, or dead code.
Product contract
- The distribution name is
clockify-python-115. - The import package for the SDK is
clockify. - The import package for MCP is
clockify_mcp. - Python 3.11, 3.12, 3.13, and 3.14 are supported.
- The SDK has 168 operations on 29 resources.
- The SDK has 168 explicit public async methods.
- The default MCP server is the full server: 186 tools.
- The full server has 60 raw read tools and 104 raw write tools.
- The full server has 18 workflows and 4 orientation tools.
CLOCKIFY_MCP_READ_ONLY=trueserves the 65-tool read-only build.- Every guarded write requires sealed user approval of the exact request.
- stdio is the default transport;
--httpserves Streamable HTTP. - The project is independent and unofficial.
- Do not imply endorsement by CAKE.com or Clockify.
Sources of truth
- Use current source and tests as executable evidence.
- Use
src/clockify/operations/registry.pyfor runtime operation truth. - Use
docs/port/OPERATION_PORT_MANIFEST.mdfor endpoint mappings. - Use
docs/port/MCP_WRITE_SAFETY_PLAN.mdfor MCP write conditions. - Use
docs/api-deviations.mdfor known API behavior differences. - Use
docs/api-coverage.mdfor the supported API surface. - Use
docs/architecture.mdfor dependency direction. - Use
SECURITY.mdfor security guarantees and reporting. - Use
CHANGELOG.mdfor user-visible version history. - Treat old audits and implementation receipts as non-product history.
- Do not restore removed campaign documents to the repository.
- Verify documentation claims against the current checkout.
Repository boundary
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 · 312 lines · 2,929 tokens per session scan A 63f408dd5188
clockify-python AGENTS.md is an instructions file published in the GitHub repository apet97/clockify-python (0 stars, last pushed 19d ago), licensed MIT. It adds 2,929 tokens to every session, about $0.0146 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
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.