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.
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/onboarding-pack)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/onboarding-pack"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/onboarding-pack/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/onboarding-pack"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/onboarding-pack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.02209 |
| Opus 5 | $0.00005 | $0.01104 |
| Sonnet 5 | $0.00002 | $0.00442 |
| Haiku 4.5 | $0.00001 | $0.00221 |
Grade A, and why
onboarding-pack 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 12d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:onboarding-pack
Trigger
/architect:onboarding-pack — run at any handoff point: agency kickoff after ideation, first hire, or post-scaffold developer onboarding.
Purpose
Generate a comprehensive developer onboarding document for handing off to a development agency, bringing on the first engineer, or onboarding new developers to a running codebase. Assembles architecture context, tech stack decisions, environment setup, and coding conventions into a single "start here" document. Adapts automatically to the project stage — pre-scaffold outputs a setup brief for agencies; post-scaffold outputs a full codebase guide.
Workflow
Step 1: Gather Project Context
Read in this order:
architecture-output/_state.json— read first if it exists; provides compactproject(name, description, stage),tech_stack(frontend, backend, database, auth, deployment),components(names, types, ports, frameworks),entities(field names per entity), anddesign(palette and fonts). Use these instead of reading full markdown files for tech stack, component list, and entity information.- SDL file — architecture style, detailed component config, auth strategy, data model relationships; only read SDL sections not covered by
_state.json(e.g. inter-service communication, environments, observability config). Checksolution.sdl.yamlfirst; if absent, readsdl/README.mdthen the relevant module files. - Executive summary —
architecture-output/executive-summary.md(if exists, typically small) - API docs —
architecture-output/api-docs.md(if exists, typically small) - ADR files — any
adr-*.mdfiles inarchitecture-output/ - Scaffold plan —
architecture-output/scaffold-plan.md(if exists) - Environment config —
.env.example,docker-compose.yml - Coding rules —
CLAUDE.md,.cursorrules,copilot-instructions.md,.eslintrc.*,tsconfig.json - CI/CD config —
.github/workflows/,azure-pipelines.yml - Package files — root
package.json, componentpackage.jsonfiles - Scaffold report —
.archon/scaffold-report.json(component status)
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.
- 12d ago First seen · 206 lines · 10 tokens per session scan A 23d32df0ab33
onboarding-pack is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 2,209 once invoked, about $0.0001 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 commands, from other repositories
nyann:bootstrap
Explicit entry point for nyann's bootstrap flow. Does exactly what the natural-language trigger ("set up this project") does, but skips intent detection so users who prefer slash commands can opt in directly.
nyann:suggest
Analyze a repository and suggest profile updates based on installed dependencies, config files, repo structure, and git history patterns.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.