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/hannsxpeter/scriveno/archgit clone --depth 1 https://github.com/hannsxpeter/scrivenoWrote 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/agents/hannsxpeter/scriveno/arch)<a href="https://agentmods.dev/agents/hannsxpeter/scriveno/arch"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/arch.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00424 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
arch 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- quality — 88% identical, 18 lines differ
What it actually says
Scope
(stub) Capture project-specific guidance for arch.
Context
(stub) Fill with facts an agent cannot reliably infer from code alone.
Decisions
(none)
Rules
(none)
Workflows
(none)
Watchouts
(none)
Touchpoints
(none)
Gaps
- This pillar is a stub. Ask before making durable arch decisions.
Godpowers artifact sources
- Sync mode: proposed for review.
- Related artifact:
.godpowers/arch/ARCH.mdx. - Rule: keep this pillar aligned when these artifacts change durable arch truth.
Extracted durable signals
From .godpowers/arch/ARCH.mdx:
- [DECISION] This artifact was generated from imported planning-system context.
- [DECISION] Treat this artifact as a Godpowers seed until a specialist command validates or rewrites it.
- [DECISION] Imported source files remain historical evidence, not Godpowers source of truth.
- [HYPOTHESIS] legacy planning source .planning/archive/01-12-historical-REVIEW-FIX.md may inform this artifact.
- [HYPOTHESIS] Imported signal from .planning/archive/01-12-historical-REVIEW-FIX.md: Historical Phases 1-12: Review Fix Summary.
- [HYPOTHESIS] Imported signal from .planning/archive/01-12-historical-REVIEW-FIX.md: Scope.
- [HYPOTHESIS] Imported signal from .planning/archive/01-12-historical-REVIEW-FIX.md: Fixed Findings.
- [HYPOTHESIS] legacy planning source .planning/archive/MILESTONE_SUMMARY-v1.0.md may inform this artifact.
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.
- 3d ago First seen · 62 lines · 0 tokens per session scan A 9e4cce096375
arch is an agent published in the GitHub repository hannsxpeter/scriveno (9 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 424 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
pr-creator
Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n \nContext…
nolan
HR / Talent Acquisition. Use proactively when the user asks to hire a new specialist, asks "can the team do X" where X isn't covered by the current six, or when Larry detects a gap. Owns SOP-001 and the agent-index. Drafts AGENTS.md contracts AND .claude/agents/ .md shims for every hire.
penn
Journal Writer. Use proactively when the user dumps thoughts, feelings, daily reflections, voice memos, screenshots, business cards, braindumps, or anything from Team Inbox/. Captures into PKM/Journal/YYYY/MM/ and routes structured entities into PKM/CRM and PKM/My Life. Owns WS-001 (daily journaling).
pax
Senior Researcher. Use proactively for any task that needs cross-source verification before action — hire research briefs (mandatory step in SOP-001), unfamiliar tool/format research before WS-002 imports, market or competitor surveys, due-diligence on tools/people/orgs {{USERNAME}} is evaluating, anti-pattern…
maintainer-agent
Expert codebase maintainer. Proactively synchronizes documentation with the actual codebase and fixes linting/formatting issues using Trunk. Use this whenever the repository state changes or to ensure project standards.
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.