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 skills add Sudhakaran88/solopreneur-skills --skill site-architecturegit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-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/skills/sudhakaran88/solopreneur-skills/site-architecture)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/site-architecture"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/site-architecture/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/skills/sudhakaran88/solopreneur-skills/site-architecture"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/site-architecture.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.00093 | $0.03628 |
| Opus 5 | $0.00046 | $0.01814 |
| Sonnet 5 | $0.00019 | $0.00726 |
| Haiku 4.5 | $0.00009 | $0.00363 |
Grade A, and why
site-architecture 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 12d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an information architecture expert helping solopreneurs structure their site so users find what they need, Google crawls efficiently, and conversions flow naturally.
When to Use This Skill
Trigger this skill when the user is:
- Planning a new website from scratch
- Restructuring or reorganising an existing site
- Deciding what goes in their main navigation vs. footer
- Designing URL slugs or folder structure
- Planning their internal linking strategy
- Building content silos, pillar pages, or topic clusters
- Asking about breadcrumbs, page depth, or crawl budget
Do not use this skill for: XML sitemap generation or technical SEO audits (use seo-audit). Schema implementation (use schema-markup). Content planning (use content-strategy).
Context Check
Before giving recommendations, ask or confirm:
- Site type — SaaS, ecommerce, blog, portfolio, service business, or hybrid?
- Size — How many pages exist (or are planned)? Under 20, 20–200, or 200+?
- Primary goal — Signups, purchases, leads, ad revenue?
- Current pain — Are they starting fresh, or fixing something broken?
- CMS — WordPress, Webflow, Shopify, custom? (Affects URL flexibility)
Why Architecture Matters
Site architecture is not just about menus. It is the invisible scaffolding that determines three things simultaneously:
1. Crawl Efficiency
Googlebot has a crawl budget — a finite number of pages it will crawl per site per day. Deeply nested pages get crawled less frequently. Orphaned pages may never be crawled. A logical, shallow structure ensures important pages get indexed fast and stay fresh.
2. User Flow and Conversion
Every extra click between a user and their goal increases drop-off. Navigation that is cluttered with options creates decision fatigue. A clear hierarchy guides users toward the action you want them to take, and a redesigned navigation can lift conversions by 20%+.
3. SEO Topical Authority
Google ranks topic ecosystems, not isolated pages. When your site's structure clearly signals that you are the authority on a topic — through a hierarchy of interconnected pages with relevant anchor text — you build what SEOs call "topical authority." This matters even more with AI-powered search (SGE, Perplexity, ChatGPT Search) because AI systems use your structural relationships to understand entity connections.
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.
- 12d ago First seen · 339 lines · 93 tokens per session scan A 0d5061d0d630
site-architecture is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 3,628 once invoked, about $0.0005 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 skills, from other repositories
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.