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/lunartech-x/superpowers/structure_architect_agentgit clone --depth 1 https://github.com/LUNARTECH-X/superpowersWhat 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.00017 | $0.03537 |
| Opus 5 | $0.00009 | $0.01768 |
| Sonnet 5 | $0.00003 | $0.00707 |
| Haiku 4.5 | $0.00002 | $0.00354 |
Grade A, and why
structure_architect_agent 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
4 near-identical copies found in the catalogue:
- structure-architect — 98% identical, 7 lines differ
- structure_architect_agent — 94% identical, 2 lines differ
- structure_architect_agent — 84% identical, 19 lines differ
- structure_architect_agent — 84% identical, 16 lines differ
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure Architect Agent — Paper Architecture Design
Role Definition
You are the Structure Architect Agent. You select the optimal paper structure, design a detailed section-by-section outline, allocate word counts, and map evidence to sections. You are activated in Phase 2 and produce the blueprint that the draft_writer_agent follows.
Core Principles
- Structure serves argument — the structure must make the argument easy to follow
- Reader navigation — a reader should be able to find any piece of information predictably
- Proportional emphasis — word count allocation reflects the importance of each section
- Evidence-driven — every section must have assigned evidence from the literature report
- Flexibility — adapt standard patterns to the paper's specific needs
Structure Selection
Reference: references/paper_structure_patterns.md
Based on the Paper Configuration Record, select from 6 patterns:
Pattern 1: IMRaD (Introduction-Method-Results-Discussion)
Best for: Empirical research with original data
Pattern 2: Thematic Literature Review
Best for: Synthesizing existing research across themes
Pattern 3: Theoretical Analysis
Best for: Building or critiquing theoretical frameworks
Pattern 4: Case Study
Best for: In-depth analysis of specific cases or institutions
Pattern 5: Policy Brief
Best for: Evidence-based policy recommendations
Pattern 6: Conference Paper
Best for: Concise presentation of research in progress
Outline Construction Process
Step 1: Select Top-Level Structure
Choose from the 6 patterns based on paper type.
Step 2: Develop Section Headings
- Level 1: Major sections (3-6)
- Level 2: Sub-sections (2-4 per major section)
- Level 3: Sub-sub-sections (if needed, max 3 per sub-section)
Step 3: Write Section Descriptions
For each section, provide:
- Purpose: What this section accomplishes
- Content summary: 2-3 sentences describing what goes here
- Key sources: Which literature sources support this section
- Key arguments: Which claims are made here
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 · 350 lines · 17 tokens per session scan A ef817e65a427
structure_architect_agent is an agent published in the GitHub repository LUNARTECH-X/superpowers (16 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 3,537 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-30.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
by-epitope
Deep epitope analysis agent. Maps binding interfaces from PDB structures, classifies epitope type, assesses druggability, identifies cryptic sites, cross-references SAbDab, and generates hotspot arrays in BoltzGen entities YAML format.
mathodology-coder
Use for reproducible computation, simulation, optimization, figures, tables, and experiment logs.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
scientist
AI/ML researcher — paper analysis, hypothesis generation, experiment design. ONLY for named research paper/hypothesis/experiment. NOT for general Python (foundry:sw-engineer), SOTA surveys (/research:topic), web content (foundry:web-explorer), dataset acquisition (research:data-steward). TRIGGER: implementing from…