server_structure_template

A fill-in document template for defining a project's server architecture, data models, storage, authentication, and data flow. It includes examples for decentralized and traditional systems, including databases and Holochain.

In plain words
What is it for?
Use it to document data distribution, hierarchy, authentication, validation rules, known issues, and the relationship between server code and the rest of the project.
Why use it?
It gives a project team one place to describe how the server works and what rules its data follows. This reduces ambiguity when building or reviewing the server structure.

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/server_structure_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 418 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.00418
Opus 5 $0.00000 $0.00209
Sonnet 5 $0.00000 $0.00084
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

server_structure_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/server_structure_template.md · 25 lines

What it actually says

Server Structure Template

This document defines the server architecture, data models, and rules for [Project Name], ensuring scalable and secure data management.

Guidelines for Filling Out This Template

  • Replace [Project Name] with your project's name.
  • For decentralized: Detail layers (e.g., client, DHT, blockchain); for traditional: DB schemas.
  • Use diagrams (Mermaid ER) for data flows.
  • Include validation rules (e.g., "Max [limit] entries").
  • Adapt for tech: For [server: e.g., Holochain], add zome examples; for SQL, schemas.
  • Reference repo structure: Store this in /docs/agents/server_structure_doc.md; link to /file_structure.md for server files in /source/[server-dir]/.

Data Distribution and Hierarchy

[Client-Side: Structures like {memory: obj}; [Server Layer]: JSON entries; etc. Include Mermaid diagram. Assumptions: [e.g., "Local storage limits"]; Known Issues: [e.g., "Sync delays"].]

Mermaid Diagram: [e.g., erDiagram; CLIENT ||--|| SERVER : syncs; Assumptions: [e.g., "Batch updates"]; Known Issues: [e.g., "Conflict resolution"].]

Authentication Logic

[Process: e.g., "[Auth method] sign-in"; Data Flow: "Key links to [storage]." Example: Code snippet for login. Assumptions: [e.g., "JWT expiry"]; Known Issues: [e.g., "Token revocation"].]

Data Management Rules

[Client: "Temporary state"; Validation: "[Server] rules for integrity." Example: Schema or zome function. Assumptions: [e.g., "Batch sync"]; Known Issues: [e.g., "Conflict resolution"].]

Edge Cases

[Network Disconnect: "Cache in [storage]"; etc. Include handling code. Assumptions: [e.g., "Offline tolerance"]; Known Issues: [e.g., "Re-sync failures"].]

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 · 25 lines · 0 tokens per session scan A 1aa11ddd7f5b

Subscribe to this mod's changes

server_structure_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 418 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.