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 DorianSchlede/nexus-template --skill update-workspace-mapgit clone --depth 1 https://github.com/DorianSchlede/nexus-templateWrote 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/dorianschlede/nexus-template/update-workspace-map)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/update-workspace-map"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/update-workspace-map/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/dorianschlede/nexus-template/update-workspace-map"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/update-workspace-map.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.00015 | $0.01126 |
| Opus 5 | $0.00008 | $0.00563 |
| Sonnet 5 | $0.00003 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
update-workspace-map 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 9d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Workspace Map
Ensure workspace-map.md stays synchronized with actual 04-workspace/ folder structure up to 3 levels deep.
Purpose
The workspace-map.md file helps AI understand your custom folder organization in 04-workspace/. When it becomes stale (folders added/removed/reorganized but not documented), AI navigation becomes unreliable.
This skill:
- Scans workspace structure 3 levels deep (root → level 1 → level 2 → level 3)
- Compares actual folders with documented folders at all levels
- Identifies mismatches (missing or extra folders, incorrect nesting)
- Provides detailed structure report with depth indicators
- Guides you through comprehensive updates
- Validates accuracy after changes
Improvements over v1:
- [OK] 3-layer deep scanning (vs 1 layer)
- [OK] Hierarchical validation (parent-child relationships)
- [OK] File detection (warns about files that should be documented)
- [OK] Depth indicators in reports (├──, │ ├──, │ │ ├──)
- [OK] Comprehensive documentation prompts for nested structures
When to use:
- You reorganized 04-workspace/ folders
- You notice AI can't find your folders
- During onboarding (Build 03, Task 5.6)
- As part of regular maintenance (via close-session)
Workflow
Step 1: Scan Actual Workspace Structure (3 Levels Deep)
Scan workspace recursively (up to 3 levels):
find 04-workspace -maxdepth 3 -type d | sort
Parse into hierarchical structure:
04-workspace/
├── input/
│ ├── skills/
│ │ ├── examples/
│ │ └── templates/
│ └── docs/
├── clients/
│ ├── acme/
│ │ ├── deliverables/
│ │ └── notes/
│ └── globex/
└── templates/
Also scan for important files (for documentation warnings):
find 04-workspace -maxdepth 3 -type f -name "*.md" -o -name "README*" | sort
Store:
- ACTUAL_STRUCTURE (tree with 3 levels)
- IMPORTANT_FILES (markdown/README files)
Exclude:
- Hidden folders (., .., .git, .DS_Store)
- workspace-map.md itself
- System folders
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 161 lines · 15 tokens per session scan A 5ec470418baf
update-workspace-map is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 1,126 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.