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/technology_stack_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.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
technology_stack_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 yesterday.
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technology Stack Template
This document lists the technologies, packages, dependencies, APIs, and tools for [Project Name], with purposes and documentation links to guide implementation.
Guidelines for Filling Out This Template
- Replace [Project Name] with your project's name.
- Use tables for packages/tools (columns: Package, Purpose, Docs).
- Categorize by layer (front-end, back-end, tools) for clarity.
- Include installation notes (e.g., "npm install X") and version pins (e.g., "^1.0.0").
- For multi-lang projects: Separate by language (e.g., JS vs. Python sections).
- Update for changes: Add new entries, note deprecations.
- Reference repo structure: Store this in /docs/agents/tech_stack_doc.md; link to /file_structure.md for dep locations in /source/.
Front-End
[Table: e.g., | HTML5 Canvas | Rendering [element] | MDN Docs | Installation: Native browser API. Assumptions: [e.g., "Browser support ES6+"]; Known Issues: [e.g., "IE11 incompatibility"].]
Back-End
[Table: e.g., | [Backend: e.g., Holochain hClient] | [Purpose] | Docs | Installation: npm install X. Assumptions: [e.g., "Local conductor"]; Known Issues: [e.g., "Beta mobile support"].]
Data Storage
[Table: e.g., | IndexedDB | Client caching | MDN Docs | Usage: For offline assets. Assumptions: [e.g., "5MB limit"]; Known Issues: [e.g., "Private browsing clears data"].]
Development Tools
[Table: e.g., | npm | Package management | Docs | Installation: With Node.js. Assumptions: [e.g., "v18+"]; Known Issues: [e.g., "Lockfile conflicts"].]
Optional: Jupyter notebooks (dev exploration)
| Package | Purpose | Docs |
|---|---|---|
| JupyterLab | Browser UI for dev notebooks under notebooks/ |
jupyter.org |
| ipykernel | Project .venv kernel for notebooks |
ipykernel |
| httpx | Fetch external or local API data in notebooks | python-httpx.org |
| nbstripout | Strip notebook outputs on git commit | nbstripout |
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.
- yesterday First seen · 37 lines · 0 tokens per session scan A 3a9f826a72fe
technology_stack_template is an agent published in the GitHub repository atebites-hub/PJTemplate (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.