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/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/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/agents/hamzabellouch/agent-skills/structure_architect_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/structure_architect_agent.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.00017 | $0.03974 |
| Opus 5.5 | $0.00007 | $0.01590 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (8 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 3,974 once invoked, about $0.0001 per session on Opus 5.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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.