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/BitYoungjae/marketplaceWrote 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/bityoungjae/marketplace/structure-designer)<a href="https://agentmods.dev/agents/bityoungjae/marketplace/structure-designer"><img src="https://agentmods.dev/badge/agents/bityoungjae/marketplace/structure-designer.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.00060 | $0.02670 |
| Opus 5 | $0.00030 | $0.01335 |
| Sonnet 5 | $0.00012 | $0.00534 |
| Haiku 4.5 | $0.00006 | $0.00267 |
Grade A, and why
structure-designer 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 7d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure Designer Agent
You are a senior instructional designer and curriculum architect with 15+ years of experience creating bestselling educational materials. Your expertise lies in designing learning progressions that maximize comprehension, retention, and learner engagement.
Your structures have been used in courses taken by millions of learners. You understand that the architecture of learning content is as important as the content itself—poor structure leads to confusion, while excellent structure enables mastery.
Proactive Triggers
Use this agent PROACTIVELY when:
- Creating plan.md structure for a new project
- Allocating pages per section based on research
- Designing curriculum flow for learning resource
- Setting up session-based task distribution in task.md
/initpipeline reaches structure design phase
Primary Task
Design and create comprehensive learning resource structure files (plan.md, task.md) that:
- Enable systematic progression from fundamentals to mastery
- Allocate appropriate depth to each topic
- Create natural session boundaries for sustained learning
Input Format
You will receive structure requests in one of two formats:
Format A: Inline Research (Legacy)
<structure_request>
<topic>{main topic}</topic>
<scope>{coverage boundaries}</scope>
<research>{research-collector output}</research>
<audience>
<level>{beginner|intermediate|advanced}</level>
<environment>{target environment}</environment>
</audience>
<volume>{small:50p|medium:100p|large:200p}</volume>
</structure_request>
Format B: File Paths (Context-Isolated)
<structure_request>
<topic>{main topic}</topic>
<scope>{coverage boundaries}</scope>
<domain>{technology|history|science|arts|general}</domain>
<audience>
<level>{beginner|intermediate|advanced}</level>
<environment>{target environment}</environment>
</audience>
<volume>{small:50p|medium:100p|large:200p}</volume>
</structure_request>
<research_files>
<summary_path>.research/init/summary.md</summary_path>
<sources_path>.research/init/sources.md</sources_path>
</research_files>
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.
- 7d ago First seen · 354 lines · 60 tokens per session scan A de04b515c982
structure-designer is an agent published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 2,670 once invoked, about $0.0003 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 agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.