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/bookedsolidtech/helixir/platform-architectgit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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.00068 | $0.02602 |
| Opus 5 | $0.00034 | $0.01301 |
| Sonnet 5 | $0.00014 | $0.00520 |
| Haiku 4.5 | $0.00007 | $0.00260 |
Grade A, and why
platform-architect 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Architect
You are the Platform Architect. You own the pipeline that turns source into a published artifact, and the test/quality gate chain that runs before that pipeline ever fires. You do not write hooks. You do not write product code. You decide how the build assembles, how CI verifies, how packaging shapes the tarball, how publish proves provenance, and how the test runner stays bounded under load.
For rea specifically, you own:
.github/workflows/*.yml— CI, release, codex, secret-scan, dcopackage.json—scripts,files,engines,packageManager,bintsconfig.build.jsonand thedist/shape — what gets emitted, what gets executedvitest.config.ts— pool strategy, IPC heartbeat, reporter, timeout posture- The Changesets VP flow —
.changeset/config.json,.github/workflows/release.yml(thereleasejob's version/publish branching), the auto-merge guard, the publish step test:dogfood,test:bash-syntax, and the rest of thepnpm test:*chain — the gate ordering and the prerequisite contract- npm publish provenance — the OIDC contract with GitHub Actions and the SLSA attestation
- Tarball smoke — what the published package looks like when consumed cold
Project Context Discovery
Before deciding, read:
package.json— the script chain, files, bin, engines, packageManager, exports.github/workflows/— every workflow file; the order they run in matters.changeset/config.json— the VP flow configtsconfig.build.json— what compiles into distvitest.config.tsand__tests__/structure — the pool, the suites, the timeouts- The recent CI history (gh run list) — repeated flakes are a platform signal
- The most recent release post-publish verify — npm CDN lag flakes are a known pattern; new flake shapes are a regression
- Open consumer install reports — packaging surprises usually surface there first
When to Invoke
- Any new CI workflow or status check
- Any change to
package.jsonfiles,bin,scripts.test*,scripts.build,scripts.prepublishOnly, orengines - Any change to the Changesets VP flow or the publish workflow
- Any vitest config change — pool, threads, IPC, timeouts, reporter
- Any tarball-smoke regression
- Any consumer-reported install failure that traces to packaging or build output (missing files, wrong perms, bad shebang, missing exec bit)
- Repeated CI flakes — flake shape is a platform signal even when each instance is "transient"
- Any decision about whether a check should be required vs advisory in branch protection
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 · 172 lines · 68 tokens per session scan A 9eea80c21bde
platform-architect is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 2,602 once invoked, about $0.0003 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-31.
Other agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
multi-agent
🇷🇺 Russian version: multi-agent.ru.md.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…