agentmods.dev

overtime_calculator: Instructions file for Codex

AGENTS.md

overtime_calculator AGENTS.md is an instructions file for Codex, OpenCode from jiangdengke/overtime_calculator. It costs 489 tokens per session, scanned A, original, Apache-2.0.

A project-specific instruction file for a Flutter app, a framework for building mobile, web, and desktop applications with Dart. It documents the app's folders, commands, naming rules, and testing practices.

In plain words
What is it for?
Use it when working on the overtime_calculator repository. It covers dependency installation, local runs, automated tests, code analysis, release builds, formatting, and file organization.
Why use it?
It gives coding agents the repository's conventions and commands in one place. This reduces guesswork about how to build, check, and organize the project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is jiangdengke/overtime_calculator's own configuration. It tells Codex and OpenCode how to work on overtime_calculator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything overtime_calculator configures →

not rated 2repo 6mo ago A scan 489 tokens original Apache-2.0
View source ↗ jiangdengke/overtime_calculator
Reuse

Borrowing it

Nothing to install: this file belongs to jiangdengke/overtime_calculator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jiangdengke/overtime_calculator/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/jiangdengke/overtime_calculator

Made for: Codex, OpenCode.

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

agentmods badge for overtime_calculator AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jiangdengke/overtime_calculator/agents-md.svg)](https://agentmods.dev/instructions/jiangdengke/overtime_calculator/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/jiangdengke/overtime_calculator/agents-md"><img src="https://agentmods.dev/badge/instructions/jiangdengke/overtime_calculator/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 489 This file is loaded in full into every session.
When invoked 489 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00489 $0.00489
Opus 5 $0.00244 $0.00244
Sonnet 5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

Measured 7d ago against content hash 308648c577c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

overtime_calculator 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 7d 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.

AGENTS.md · 44 lines

What it actually says

Repository Guidelines

Project Structure & Module Organization

  • lib/ Flutter source
    • main.dart: app entry + Provider wiring (GlobalData)
    • models/: app state and data models (e.g. GlobalData, OvertimeRecord)
    • services/: persistence/auth/sync abstractions (SharedPreferences + placeholders)
    • screens/: top-level pages (Home/Report/Settings/Onboarding)
    • widgets/: reusable UI components
  • test/: widget/unit tests (*_test.dart)
  • docs/: screenshots and assets (e.g. docs/assets/icon.png)
  • Platform folders: android/, ios/, web/

Build, Test, and Development Commands

  • flutter pub get — install dependencies
  • flutter run — run locally on a device/emulator
  • flutter test --no-version-check — run automated tests
  • flutter analyze --no-version-check — run lints (see analysis_options.yaml)
  • flutter build apk --release --split-per-abi — build release APKs (matches CI)

Coding Style & Naming Conventions

  • Format before pushing: dart format . (Dart defaults; 2-space indentation).
  • Naming: files snake_case.dart, classes/widgets UpperCamelCase, locals lowerCamelCase.
  • Keep business logic in models/ + services/; keep UI-only code in screens//widgets/.

Testing Guidelines

  • Prefer small widget smoke tests that pump MyApp with a ChangeNotifierProvider<GlobalData>.
  • Use SharedPreferences.setMockInitialValues({}) to avoid platform IO in tests.
  • Keep tests independent: GlobalData is a singleton, so reset state via mocked prefs/setup.

Commit & Pull Request Guidelines

  • Existing history uses short messages (often “update”); use clearer, imperative subjects.
    • Example: fix: correct duplicate merge logic
  • PRs should include: a short summary, screenshots for UI changes (docs/screenshots/), and notes for any storage/model changes.

Release Notes

  • Pushing a tag matching v* triggers .github/workflows/release.yml to build and publish Android APKs to GitHub Releases.
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. 7d ago First seen · 44 lines · 489 tokens per session scan A 308648c577c3

Subscribe to this mod's changes

overtime_calculator AGENTS.md is an instructions file published in the GitHub repository jiangdengke/overtime_calculator (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 489 tokens to every session, about $0.0024 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

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,153 tokens

vscode buildNext.instructions.md

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

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

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.

langchain-ai/langchain · 4,469 tokens

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

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

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.

github/spec-kit · 7,104 tokens