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 skills/ea-toolkit/architecture-catalog/deploynpx skills add ea-toolkit/architecture-catalog --skill deploygit clone --depth 1 https://github.com/ea-toolkit/architecture-catalogWhat 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.00032 | $0.00759 |
| Opus 5 | $0.00016 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
deploy 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy to Firebase Hosting
Build and deploy the catalog UI and/or docs site to Firebase Hosting.
Arguments
$ARGUMENTSmay contain:--dry-run— Build only, skip deploy. Show what would be deployed.--target catalog— Deploy only the catalog UI--target docs— Deploy only the docs site--target all— Deploy both (default)- No arguments = build and deploy all targets
Workflow
1. Parse Arguments
Extract flags from $ARGUMENTS:
- Check for
--dry-runflag - Check for
--target <value>(default:all)
2. Validate Prerequisites
Run these checks before proceeding:
# Check Firebase CLI is installed
which firebase || echo "ERROR: Firebase CLI not installed. Run: npm install -g firebase-tools"
# Check Firebase auth
firebase projects:list --limit 1 2>&1 || echo "ERROR: Not authenticated. Run: firebase login"
# Check firebase.json exists
test -f firebase.json || echo "ERROR: firebase.json not found in project root"
If any check fails, report the error and stop.
3. Build
Based on --target:
Catalog UI (target = catalog or all):
cd catalog-ui && npm ci && npm run build
Report build output size: du -sh catalog-ui/dist
Docs Site (target = docs or all):
cd docs-site && npm ci && npm run build
Report build output size: du -sh docs-site/dist
4. Deploy (skip if --dry-run)
firebase deploy --only hosting
If targeting a specific site:
firebase deploy --only hosting:catalog
# or
firebase deploy --only hosting:docs
5. Report
On dry-run:
**Dry Run Complete**
| Target | Build | Size |
|--------|-------|------|
| Catalog UI | OK | X MB |
| Docs Site | OK | X MB |
Ready to deploy. Run `/deploy` (without --dry-run) to push to Firebase.
On deploy:
**Deployed Successfully**
| Target | URL |
|--------|-----|
| Catalog UI | https://architecture-catalog.web.app |
| Docs Site | https://docs-architecture-catalog.web.app |
Firebase project: ea-toolkit-demo-ac513
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 · 113 lines · 32 tokens per session scan A ac8598a494fb
deploy is a skill published in the GitHub repository ea-toolkit/architecture-catalog (38 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 759 once invoked, about $0.0002 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-30.
Other skills, from other repositories
site-starter
Bootstraps a brand-new Astro + Cloudflare client site from PortableWebtoolkit site-starter templates. Use when creating a new client project folder, copying package.json/wrangler.toml, linking WebToolkit, or choosing Workers vs Pages deploy target.
portable-web-toolkit
Coordinate multi-capability work, deployment or release sequencing, and ambiguous operations in Astro and Cloudflare projects managed by Portable Web Toolkit. Use when the task crosses toolkit owners or needs routing and safety gates. Defer directly to a narrow skill when readiness, scaffolding, updating, Instagram…
site-onboarding
Checkpoint-driven hand-holding for new machines and new Astro + Cloudflare sites using Portable Web Toolkit. Use when the user is new to Cloudflare, needs host setup, API tokens, Cloudflare MCP/plugin install, Workers vs Pages choice, or a guided site-starter scaffold. Load docs/agent-skills/ONBOARDINGSTAGES.md and…
wordpress-plugin-to-emdash
Port a WordPress plugin to EmDash CMS. Use this skill when asked to migrate, convert, or port a WordPress plugin, theme functionality, or custom post type to EmDash. Provides concept mapping and implementation patterns.
huggingface-spaces
Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't…
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.