docs

A documentation-maintenance agent for an Expo mobile template. It keeps the README and capability list aligned with the project’s actual code and conventions.

In plain words
What is it for?
Use it after changing components, themes, design tokens, dependencies, conventions, or available agents, and when documentation needs updating.
Why use it?
It removes the need to manually remember which documentation sections became outdated after project changes.

Agent for Claude Code

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 agents/kitariel/expo-mobile-template/docs
Clone the repo
git clone --depth 1 https://github.com/kitariel/expo-mobile-template

Made for: Claude Code.

Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 250 The whole file, excluding the scripts and references it only reads on demand.
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.00064 $0.00250
Opus 5 $0.00032 $0.00125
Sonnet 5 $0.00013 $0.00050
Haiku 4.5 $0.00006 $0.00025

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

Security

Grade A, and why

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

.claude/agents/docs.md · 21 lines

What it actually says

You are the docs agent for this Expo mobile template.

Step 1 — read your definition. Read .agents/docs.md in the repository root. It is the complete and authoritative specification of your behaviour: which documents you own, the capability-table format, the method, and the rules. Follow it precisely.

Step 2 — read the project context. Read AGENTS.md for the stack, conventions, and current phase.

Step 3 — do the work exactly as .agents/docs.md specifies. Verify every path and command you write against the real repository before writing it.

This wrapper deliberately contains no instructions of its own, so it can never drift from .agents/docs.md. If the two ever appear to disagree, .agents/docs.md wins.

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 · 21 lines · 64 tokens per session scan A fdce8bade655

Subscribe to this mod's changes

docs is an agent published in the GitHub repository kitariel/expo-mobile-template (6 stars, last pushed 10d ago), licensed MIT. It adds 64 tokens to every session and 250 once invoked, about $0.0003 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-31.

Related

Other agents, from other repositories

ux-flow-auditor

Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…

CharlesWiltgen/Axiom · 190 tokens

gem-mobile-tester

Mobile E2E testing: Detox, Maestro, iOS/Android simulators.

mubaidr/gem-team · 22 tokens

flutter-integration-analyzer

Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…

JayCRL/MobileVC · 429 tokens

mobile-specialist

モバイルUI・プラットフォームガイドラインの専門家。 iOS HIG / Material Design準拠、レスポンシブ対応、プラットフォーム固有パターンを評価する。 ui-review チームの一員として起動される。.

sean-sunagaku/claude-code-plugin · 64 tokens

copilot

cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.

haidrrrry/compose-kotlin-agent-skills · 0 tokens

aider

Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.

haidrrrry/compose-kotlin-agent-skills · 0 tokens