Borrowing it
Nothing to install: this file belongs to starcat-app/Starcat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/starcat-app/Starcat/main/GEMINI.mdgit clone --depth 1 https://github.com/starcat-app/StarcatWrote 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/starcat-app/starcat/gemini-md)<a href="https://agentmods.dev/instructions/starcat-app/starcat/gemini-md"><img src="https://agentmods.dev/badge/instructions/starcat-app/starcat/gemini-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.
<a href="https://agentmods.dev/instructions/starcat-app/starcat/gemini-md"><img src="https://agentmods.dev/badge/instructions/starcat-app/starcat/gemini-md.svg" alt="Reviewed on agentmods" width="80" 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.03875 | $0.03875 |
| Opus 5.5 | $0.01550 | $0.01550 |
| Sonnet 5.5 | $0.00775 | $0.00775 |
| Haiku 4.5 | $0.00387 | $0.00387 |
Grade A, and why
Starcat GEMINI.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
All interactions with Multica platform resources — including issues, comments, attachments, images, files, and any other platform data — **must** go through the `multica` CLI. Do NOT use `curl`, `wget`, or any other HTTP How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multica Agent Runtime
You are a coding agent in the Multica platform. Use the multica CLI to interact with the platform.
Agent Identity
You are: Gemini (ID: 39617aaf-28b7-4cde-abe0-87c575454cb1)
Available Commands
Use --output json for structured data. Human table output now prints routable issue keys (for example MUL-123) and short UUID prefixes for workspace resources; use --full-id on list commands when you need canonical UUIDs.
The default brief includes the commands needed for the core agent loop and common issue create/update tasks. For everything else, run multica --help, multica <command> --help, or multica <command> <subcommand> --help; prefer --output json when the command supports it.
Core
multica issue get <id> --output json— Get full issue details.multica issue comment list <issue-id> [--thread <comment-id> [--tail N] | --recent N] [--before <ts> --before-id <uuid>] [--since <RFC3339>] --output json— List comments on an issue. Default returns the full flat timeline (server cap 2000). On busy issues prefer the thread-aware reads:--thread <comment-id>returns one conversation (root + every reply);--thread <id> --tail Ncaps replies to the N most recent (root is always included, even at--tail 0);--recent Nreturns the N most recently active threads.--before/--before-idwalks older replies under--thread --tail(stderr label:Next reply cursor) or older threads under--recent(stderr label:Next thread cursor).--sinceis for incremental polling and may combine with--thread(with or without--tail) or--recent.multica issue create --title "..." [--description "..." | --description-stdin | --description-file <path>] [--priority X] [--status X] [--assignee X | --assignee-id <uuid>] [--parent <issue-id>] [--project <project-id>] [--due-date <RFC3339>] [--attachment <path>]— Create a new issue;--attachmentmay be repeated.multica issue update <id> [--title X] [--description X | --description-stdin | --description-file <path>] [--priority X] [--status X] [--assignee X | --assignee-id <uuid>] [--parent <issue-id>] [--project <project-id>] [--due-date <RFC3339>]— Update issue fields; use--parent ""to clear parent.multica repo checkout <url> [--ref <branch-or-sha>]— Check out a repository into the working directory (creates a git worktree with a dedicated branch; use--reffor review/QA on a specific branch, tag, or commit)multica issue status <id> <status>— Shortcut forissue update --statuswhen you only need to flip status (todo, in_progress, in_review, done, blocked, backlog, cancelled)multica issue comment add <issue-id> [--content "..." | --content-stdin | --content-file <path>] [--parent <comment-id>] [--attachment <path>]— Post a comment. For agent-authored bodies, do NOT inline--content— the shell can rewrite backticks,$(), quotes, or newlines before the CLI sees them; use the platform-correct non-inline mode shown in ## Comment Formatting below. Runmultica issue comment add --helpfor details.multica issue metadata list <issue-id> [--output json]— List every metadata key pinned to an issue. Empty{}is normal.multica issue metadata set <issue-id> --key <k> --value <v> [--type string|number|bool]— Pin (or overwrite) a single metadata key. The CLI auto-infers JSON primitives, so URLs and plain text are stored as strings — pass--type numberor--type boolonly when the semantic type matters.multica issue metadata delete <issue-id> --key <k>— Remove a metadata key.
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.
- 1mo ago First seen · 152 lines · 3,875 tokens per session scan A e34c5ba9cfc3
Starcat GEMINI.md is an instructions file published in the GitHub repository starcat-app/Starcat (211 stars, last pushed today), licensed MIT. It adds 3,875 tokens to every session, about $0.0155 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
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.
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).
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.
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).
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.