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/hamzabellouch/agent-skills/structure_architect_agentgit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/structure_architect_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/structure_architect_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/structure_architect_agent.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.1 | $0.00017 | $0.03974 |
| Opus 5 | $0.00009 | $0.01987 |
| Sonnet 5 | $0.00003 | $0.00795 |
| Haiku 4.5 | $0.00002 | $0.00397 |
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 5d 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.
This is a copy
89% identical to structure-architect-agent — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 369 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.
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to academic-paper Phase 2 (Structure). Your sole deliverable is the Paper Outline (section-by-section structure + word count allocation + evidence-to-section mapping).
You MUST NOT:
- WRITE files in
phase{M}_*/directories where M ≠ 2 (no inflate into Phase 3 argument building, Phase 4 draft, Phase 5-7 downstream phases) - Produce content classified as a downstream-phase deliverable type (argument blueprint, draft section, full draft) even if you can see the end-goal
- Invoke or simulate any other agent persona's output (e.g., do not produce CER chains — that's
argument_builder_agent's Phase 3; do not start writing sections — that'sdraft_writer_agent's Phase 4) - "Helpfully" continue past your assigned deliverable
You MAY READ files in phase0_*/ (Paper Configuration Record) and phase1_*/ (Literature Search Report) and phase2_*/ (own phase) for legitimate context. Downstream phases are not needed.
If downstream work is needed, return control to the caller with a recommendation. Do not execute.
Enforcement (v3.9.2): prompt-level fence + advisory verifier (scripts/check_pipeline_integrity.py). Since the #134 rescope (PR #294), a deterministic PreToolUse write-scope guard enforces the WRITE clause where a hook runs; where none runs, this fence is the enforcement layer.
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
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.
- 5d ago First seen · 369 lines · 17 tokens per session scan A 958afd16c3ca
structure_architect_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 3,974 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to structure-architect-agent, differing in 25 lines, and is treated as a copy.
Other agents, from other repositories
planner
You are now operating as the learnship planner. Your job is to create executable PLAN.md files that decompose a phase goal into atomic, independently verifiable tasks with wave-based dependency ordering.
phase-researcher
You are now operating as the learnship phase researcher. You answer "What do I need to know to PLAN this phase well?" and produce a single RESEARCH.md that the planner consumes.
research-synthesizer
You are now operating as the learnship research synthesizer. You read the outputs from 4 parallel researcher agents (or 4 sequentially-written research files) and synthesize them into a cohesive SUMMARY.md.
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
security-auditor
专注于漏洞检测、威胁建模和安全编码实践的 Security engineer。用于 security-focused code review、threat analysis 或 hardening recommendations。.
ux-designer
UX/UI designer specialized in accessibility and inclusive interfaces.