Minitask: Instructions file for Codex

AGENTS.md

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

A repository instruction file for the Minitask Android project. It records where code belongs, how to build and test the app, and the project's Kotlin and Android coding rules.

In plain words
What is it for?
Use it when developing the Android app, running Gradle builds and tests, checking code quality, or updating Compose screenshot baselines.
Why use it?
It gives coding agents the project-specific context needed to make changes in the right module and run the correct checks.

Instructions file for CodexOpenCode

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

This is costular/Minitask's own configuration. It tells Codex and OpenCode how to work on Minitask 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 Minitask configures →

Reuse

Borrowing it

Nothing to install: this file belongs to costular/Minitask. 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/costular/Minitask/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/costular/Minitask

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 Minitask AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/costular/minitask/agents-md/github.svg)](https://agentmods.dev/instructions/costular/minitask/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/costular/minitask/agents-md"><img src="https://agentmods.dev/badge/instructions/costular/minitask/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Minitask AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/costular/minitask/agents-md"><img src="https://agentmods.dev/badge/instructions/costular/minitask/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 679 This file is loaded in full into every session.
When invoked 679 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.00679 $0.00679
Opus 5.5 $0.00272 $0.00272
Sonnet 5.5 $0.00136 $0.00136
Haiku 4.5 $0.00068 $0.00068

Measured 1mo ago against content hash bbf96d23eeb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Minitask 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 1mo 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 · 40 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • app/ contains the Android app; unit and instrumentation suites sit under src/test and src/androidTest.
  • core/* supplies shared UI, design, analytics, logging, notifications, and core/testing utilities.
  • feature/* hosts vertical slices (agenda, settings, detail, onboarding); keep new flows in their own feature module.
  • data/ handles repositories and persistence; common/tasks holds task-domain models.
  • build-logic/ ships custom Gradle convention plugins; screenshot_testing/, scripts/, and benchmarks/ cover snapshot + baseline tooling.

Build, Test, and Development Commands

  • ./gradlew assembleDebug builds a debuggable APK.
  • ./gradlew testDebugUnitTest runs JVM unit tests.
  • ./gradlew connectedAndroidTest launches instrumentation tests with AtomTestRunner (device/emulator required).
  • ./gradlew detekt lintDebug enforces Kotlin + Android linting.
  • ./scripts/verify-screenshots.sh compares Compose snapshots; record-screenshots.sh refreshes baselines.

Coding Style & Naming Conventions

  • Kotlin uses the official style (kotlin.code.style=official), 4-space indents, trailing commas when it aids diffs.
  • Prefer PascalCase for types, camelCase for members, snake_case for resources; Compose previews belong in *Preview.kt.
  • Keep modules isolated: share code through core/common, not direct feature cross-deps.
  • Detekt (atomtasks.detekt) runs locally and in CI; resolve warnings before pushing.

Testing Guidelines

  • Co-locate unit tests with source modules and lean on core/testing for coroutine and Hilt helpers.
  • Place UI and integration suites in src/androidTest; rely on Compose test APIs and stable semantics.
  • Snapshot updates need new images in app/screenshots/ and screenshot_testing/, plus a PR note.
  • Aim for unit coverage on new logic and add an instrumentation or snapshot check for user-facing UI.

Commit & Pull Request Guidelines

  • Commits stay short and imperative (Fix hardcoded string, Update theme), referencing issues as (#123) when needed.
  • Rebase or tidy history before opening a PR; avoid merge commits.
  • PR descriptions should state intent, local testing, and UI impact (attach screenshots or screencasts).
  • Link issues, call out config or feature flag changes, and note any follow-up work.
  • Add release-note-worthy changes to CHANGELOG.md under ## [Unreleased], using the existing Keep a Changelog categories and markdown format.
  • Do not manually promote Unreleased, add release dates, or create the next empty Unreleased section; the release workflow handles that when a tag is created, committing the promotion to a release pull request for main.

Read the full file on GitHub · 40 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. 1mo ago First seen · 40 lines · 679 tokens per session scan A bbf96d23eeb8

Subscribe to this mod's changes

Minitask AGENTS.md is an instructions file published in the GitHub repository costular/Minitask (12 stars, last pushed 6d ago), licensed Apache-2.0. It adds 679 tokens to every session, about $0.0027 per session on Opus 5.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-09-04.

Related

Other instructions, from other repositories

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 · 9,649 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,549 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens