app_flow_template

A planning template for mapping an app’s screens, user actions, data exchanges, and error paths. It can also record these flows as Mermaid diagrams, which are text-based process drawings.

In plain words
What is it for?
Use it to document page navigation, single-page app state changes, offline behavior, API request flows, or game loops in a project document.
Why use it?
It helps teams describe how an app behaves before building or changing it, so missing transitions and failure cases are easier to spot.

Agent

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/atebites-hub/pjtemplate/app_flow_template
Clone the repo
git clone --depth 1 https://github.com/atebites-hub/PJTemplate
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 539 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.00000 $0.00539
Opus 5 $0.00000 $0.00269
Sonnet 5 $0.00000 $0.00108
Haiku 4.5 $0.00000 $0.00054

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

Security

Grade A, and why

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

docs/agents/app_flow_template.md · 27 lines

What it actually says

App Flow Template

This document describes the user interface flows, state transitions, and data interactions for [Project Name], ensuring seamless navigation and consistency.

Guidelines for Filling Out This Template

  • Replace [Project Name] with your project's name.
  • Use simple, narrative language—no bullets; be painfully specific (e.g., "User clicks button X, screen Y appears").
  • For multi-page/SPA apps: Detail page transitions; for games: Describe state loops (e.g., exploring to [action]).
  • Include error paths (e.g., "If offline, show cached view").
  • Adapt for tech: For PWAs, note Service Worker caching; for APIs, focus on request/response flows.
  • Add diagrams (Mermaid flowcharts) for complex paths.
  • Reference repo structure: Store this in /docs/agents/app_flow_doc.md; link to /file_structure.md for UI file locations.

[Section: e.g., Launching the App]

[Narrative description of flow, e.g., "User opens browser and navigates to the site... Include data interactions and error handling. Assumptions: [e.g., "Assumes browser support"]; Known Issues: [e.g., "Slow load on 3G"].

Mermaid Diagram: [e.g., sequenceDiagram; User->>App: Click Launch; App->>User: Load Screen; Assumptions: [e.g., "Stable deps"]; Known Issues: [e.g., "Auth timeout"].]

[Section: e.g., Core App Loop]

[Detailed step-by-step, e.g., "The loop renders [element], then captures input... Describe state transitions. Assumptions: [e.g., "Assumes 60fps"]; Known Issues: [e.g., "Input lag on touch"].

Mermaid Diagram: [e.g., graph TD; Loop[Render] --> Input[Capture]; Input --> Update[State]; Update --> Loop; Assumptions: [e.g., "Async safe"]; Known Issues: [e.g., "Race conditions"].]

[Section: e.g., Data Syncing]

[Flows for server interactions, e.g., "On save, client sends to [server] via [client]... Include verification steps. Assumptions: [e.g., "Assumes API uptime"]; Known Issues: [e.g., "Batch sync delays"].

Mermaid Diagram: [e.g., sequenceDiagram; Client->>Server: Send Data; Server->>Client: Confirm; Assumptions: [e.g., "Retry logic"]; Known Issues: [e.g., "Network partition"].]

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 · 27 lines · 0 tokens per session scan A 6c115ec175e4

Subscribe to this mod's changes

app_flow_template is an agent published in the GitHub repository atebites-hub/PJTemplate (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 539 tokens. 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.