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/supremehui/-auto-accounting/agents-mdgit clone --depth 1 https://github.com/supremehui/-Auto-AccountingWrote 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.
[](https://agentmods.dev/instructions/supremehui/-auto-accounting/agents-md)<a href="https://agentmods.dev/instructions/supremehui/-auto-accounting/agents-md"><img src="https://agentmods.dev/badge/instructions/supremehui/-auto-accounting/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00503 | $0.00503 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
-Auto-Accounting 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 today.
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.
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
Communicate in Chinese.
Project Structure & Module Organization
app/is the Android application module (Kotlin + Jetpack Compose).- Kotlin sources live in
app/src/main/java/com/brycewg/pinme/with feature packages likecapture/,extract/,vllm/,notification/,widget/,db/,service/, andui/. - Android resources live in
app/src/main/res/(e.g.,drawable/,values/,xml/,raw/). - Repo-level docs/artifacts:
README.mdandLICENSE.
Build, Test, and Development Commands
Never try to use ./gradlew build.
Coding Style & Naming Conventions
- Kotlin follows the official style (
kotlin.code.style=official): 4-space indentation, no tabs. - Names: packages
lowercase, classes/objectsPascalCase, functions/variablescamelCase. - Compose:
@Composablefunctions are typicallyPascalCasefor screens/components (for example,ExtractHome). - Prefer small, focused changes; avoid formatting-only diffs unless required.
Testing Guidelines
- Unit tests:
app/src/test/...(JUnit4). - Instrumented/UI tests:
app/src/androidTest/...(AndroidX JUnit, Espresso, Compose UI test). - Name tests
*Testand focus coverage on parsing/workflow boundaries first (for example,extract/andvllm/).
Note: .gitignore currently excludes app/src/test and app/src/androidTest; update it if you intend to add tests to the repo.
Commit & Pull Request Guidelines
- Git history uses short, imperative, sentence-case summaries (for example, “Add initial project setup …”); keep commits scoped and readable.
- PRs should describe behavior changes, include screenshots for UI/widget/notification updates, and list what you tested (API level and Flyme/Meizu device if relevant).
Security & Configuration Tips
- Never commit
local.properties, API keys, or private endpoints. Configure Base URL/Model/API Key via in-app Settings; avoid hardcoding secrets inConstants.kt. - Keep Flyme-specific behavior behind capability checks and maintain non-Flyme fallbacks (see
notification/UnifiedNotificationManager.kt).
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.
- today First seen · 40 lines · 503 tokens per session scan A 11e705025278
-Auto-Accounting AGENTS.md is an instructions file published in the GitHub repository supremehui/-Auto-Accounting (7 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 503 tokens to every session, about $0.0025 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-09-04.
Other instructions, from other repositories
MarkdownView AGENTS.md
Instructions for keitaoouchi/MarkdownView, covering agents, technical components, relationships (data/event flow overview), extension points (overview) and platform / distribution.
droidconKeKotlin AGENTS.md
AGENTS.md instructions for droidconKE/droidconKeKotlin, covering agents.md, commands, module layout, stack and conventions.
skills copilot-instructions.md
Instructions for dhruvanbhalara/skills, covering project instructions & best practices, core tech stack, coding standards, architecture & data and ui & ux (design system).
compose-android-template CLAUDE.md
Claude Code instructions for ashtanko/compose-android-template, a project described as: 📱 A simple GitHub template to quickly set up an Android project using Kotlin and Jetpack Compose, getting you up and running in just seconds. Perfect for starting new apps with modern Android UI.
intentflow-ios AGENTS.md
Instructions for emrecanozturk/intentflow-ios, covering agent instructions, read first, architecture rules, commands and token budget.
SwiftfulStarterProject CLAUDE.md
Claude Code instructions for SwiftfulThinking/SwiftfulStarterProject, covering swiftfulstarterproject, architecture, build configurations, file creation and key conventions.