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.
npx agentmods add agents/atebites-hub/pjtemplate/file_structure_templategit clone --depth 1 https://github.com/atebites-hub/PJTemplateWhat 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 | $0.00000 | $0.02257 |
| Opus 5 | $0.00000 | $0.01128 |
| Sonnet 5 | $0.00000 | $0.00451 |
| Haiku 4.5 | $0.00000 | $0.00226 |
Grade A, and why
file_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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Structure Template
This document outlines the file organization for [Project Name], ensuring modularity and maintainability across source, scripts, tests, and docs.
Guidelines for Filling Out This Template
- Replace [Project Name] with your project's name.
- Customize directories for your stack (e.g., add
/source/[lang-dir]/for Python/Rust). - Use trees for visualization (Markdown code block).
- Include storage details (e.g., [storage: e.g., IndexedDB] for client).
- Adapt for languages: For Python, add
/source/api/; for JS,/source/client/. - Reference repo structure: This file defines the root layout; store it in /docs/agents/file_structure_doc.md.
Standard Repo Layout (Mandatory)
All projects must follow this root structure to ensure cleanliness and agent cohesion. Deviations require explicit user approval.
root/
├── AGENTS.md # AI agent rules and context boundaries (program)
├── User_Rules_Template.md # Platform tool bindings (Cursor/Kilo variants optional)
├── README.md # Project overview and quick start
├── .env.example # Environment variables template
├── .gitignore # Git ignore patterns (.jspace/, .taskboard/, .odw/)
├── .agents/ # Skills: memory-system, reasoning-system, taskboard-workflow; ODW + j-space symlinks
├── vendor/ # Git submodules (open-dynamic-workflows, j-space-cognition-suite)
├── package.json # Dependencies and scripts (if applicable)
├── src/ # Main application code
│ ├── client/ # Client-side code
│ │ ├── components/ # Reusable UI components
│ │ ├── pages/ # Page components/routes
│ │ ├── hooks/ # Custom React hooks (if applicable)
│ │ ├── utils/ # Client-side utilities
│ │ └── styles/ # CSS/styling files
│ └── server/ # Backend/server-side code
│ ├── routes/ # API routes/endpoints
│ ├── models/ # Data models/schemas
│ ├── middleware/ # Express middleware (if applicable)
│ ├── services/ # Business logic services
│ └── utils/ # Server-side utilities
├── notebooks/ # Dev-only Jupyter exploration (optional install)
│ ├── _bootstrap.py # Shared paths + settings for notebooks
│ ├── explore/ # Scratch notebooks
│ ├── examples/ # Reference notebooks
│ └── data/ # Local datasets (gitignored except .gitkeep)
├── scripts/ # Build and deployment scripts
│ ├── setup.sh # Initial project setup (--with-notebooks optional)
│ ├── notebook.sh # Launch JupyterLab (dev only)
│ ├── test-suite.sh # Run all tests
│ ├── build.sh # Build for production
│ └── deploy.sh # Deployment script
├── requirements-notebooks.in # Optional dev notebook deps (separate lockfile)
├── tests/ # Test suites
│ ├── unit/ # Unit tests
│ ├── integration/ # Integration tests
│ ├── e2e/ # End-to-end tests
│ ├── security/ # Security tests
│ └── performance/ # Performance tests
└── docs/ # Documentation
├── agents/ # AI agent context documents
├── code/ # Code documentation
├── tests/ # Test documentation
│ └── notebooks.md # Dev notebook workflow (optional)
└── api/ # API documentation (if applicable)
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.
- 2d ago First seen · 198 lines · 0 tokens per session scan A a3381fb1049f
file_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 2,257 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.