agentmods.dev

Autofish: Instructions file for Codex

AGENTS.md

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

Project instructions for Autofish, an Android device-control service and command-line tool for RhinoPi X1 devices. They describe the project structure, preferred and fallback execution paths, compatibility rules, and release requirements.

In plain words
What is it for?
Use them when changing Autofish's Android service, HTTP API, command-line interface, device-control routing, or skill packaging.
Why use it?
They give coding agents the project context and constraints needed to make safe changes. They also help preserve fallback behavior and keep packaged skills and documentation aligned.

Instructions file for CodexOpenCode

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

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

not rated 119repo 1mo ago A scan 684 tokens original Apache-2.0
View source ↗ felinics/Autofish
Reuse

Borrowing it

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

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/felinics/autofish/agents-md/github.svg)](https://agentmods.dev/instructions/felinics/autofish/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/felinics/autofish/agents-md"><img src="https://agentmods.dev/badge/instructions/felinics/autofish/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 Autofish AGENTS.md

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

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

Security

Grade A, and why

Autofish 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 · 76 lines

How it starts

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

AGENTS.md

Project

Autofish is an Android device control service and CLI, targeting RhinoPi X1 (Qualcomm QCS8550 ARM64).

Context

  • Read docs/ARCHITECTURE.md before making architecture-impacting changes.
  • Treat the current codebase and documented release workflow as the source of truth when docs drift.

Current Baseline

  • Service/API:
    • Android foreground service: ServiceServerService
    • HTTP surface: /api/*
  • Execution path:
    • Preferred: Shizuku + system/shell path
    • Fallback: accessibility path
    • Routing entry: ToolRouter
  • CLI:
    • Current CLI UX may evolve for AX when changes are documented and versioned.
  • Skill packaging:
    • Canonical skill path: cli/skills/autofish-control/SKILL.md
    • CLI release workflow packages that exact path

Rules

  • Respond in Simplified Chinese.
  • Use just instead of make.
  • Do not add features that are not reflected in design or release docs.
  • Hidden API reflection calls must have try-catch plus runnable fallback behavior.
  • Preserve fallback execution paths when preferred capabilities are unavailable.

Compatibility Policy

  • Default to preserving external compatibility for service APIs, CLI commands, and packaged skill paths.
  • Breaking changes are allowed only when they are intentional and governed.
  • For breaking CLI or packaging changes, update docs in the same change set:
    • docs/ when design or architecture intent changes
    • CHANGELOG.md with explicit BREAKING notes
    • command migration examples when flags, command shape, or workflow changes
  • Breaking release cadence must follow semantic versioning discipline:
    • no silent breaking changes in patch releases
    • use prerelease tags such as -rc when validating release candidates

Change Process

  • If the requested change is not covered by current docs, update the relevant docs first or in the same change set.
  • Internal refactors must keep behavior coherent and keep fallback paths runnable.
  • CLI AX work may reshape command syntax when it materially improves usability, but the change must be documented and migration-ready.
  • If the skill directory or skill filename changes, update .github/workflows/cli-release.yml in the same change.

Read the full file on GitHub · 76 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 · 76 lines · 684 tokens per session scan A ce1b317045ef

Subscribe to this mod's changes

Autofish AGENTS.md is an instructions file published in the GitHub repository felinics/Autofish (119 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 684 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-08-30.

Hardware and IoTLLMMobileai-agentandroidandroid-automationmobile-automation
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,384 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