one AGENTS.md

Project-specific instructions for an Android and Wear OS fasting tracker built with Kotlin. They describe its structure and rules for keeping the phone and watch in sync.

In plain words
What is it for?
Use them when changing fasting state, shared data, widgets, watch complications, ongoing activities, ViewModels, repositories, or project dependencies.
Why use it?
They reduce the risk of changes breaking synchronisation, leaving parts of the interface stale, or bypassing the project’s dependency and data-flow rules.

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

Made for: Codex, OpenCode.

Per session 1,070 This file is loaded in full into every session.
When invoked 1,070 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.01070 $0.01070
Opus 5 $0.00535 $0.00535
Sonnet 5 $0.00214 $0.00214
Haiku 4.5 $0.00107 $0.00107

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

Security

Grade A, and why

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

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 · 92 lines

How it starts

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

ONE Fasting Tracker

Kotlin Android + Wear OS fasting tracker. Jetpack Compose UI, Koin DI, Room DB, DataStore, Kotlin Flows. Min SDK 31.

Before You Start

  1. Read @docs/ARCHITECTURE.md for the full project structure
  2. Ask: does this change need to sync between phone and watch?

Do Not

  • Break sync between phone and watch — all fasting state changes MUST propagate via Wearable Data Layer
  • Forget UI component updates after data changes — update ALL of: widgets (WidgetUpdateManager), complications (ComplicationUpdateManager), ongoing activities (OngoingActivityService)
  • Omit timestamps in sync updates — required for conflict resolution
  • Create local-only state that should be synced — use coroutines and Flows everywhere, never blocking calls
  • Add dependencies without going through gradle/libs.versions.toml first
  • Skip Koin registration for new ViewModels or repositories
  • Filter incorrectly in listener services — always filter local events to prevent sync loops

Architecture Rules

Dependency flow

app ──→ features:dashboard:app  ──→ core
    ──→ features:profile        ──→ core
    ──→ features:settings       ──→ core
wear ──→ features:dashboard:wear ──→ core
     ──→ core

Modules

Module Purpose
:app Phone/tablet app — Compose UI, Glance widgets, WorkManager notifications
:wear Wear OS app — Wear Compose, complications, ongoing activities
:features:dashboard:app Phone dashboard / today screen feature
:features:dashboard:wear Wear OS dashboard / today screen feature
:features:profile User profile and fasting history feature
:features:settings App settings feature
:core Core models, repositories, sync services, Room DB, DataStore, constants

Read the full file on GitHub · 92 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.

  1. 2d ago First seen · 92 lines · 1,070 tokens per session scan A 55af67fc574a

Subscribe to this mod's changes

one AGENTS.md is an instructions file published in the GitHub repository charliesbot/one (20 stars, last pushed 29d ago), licensed MIT. It adds 1,070 tokens to every session, about $0.0053 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-30.