Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DojoGenesis/mcpnpx agentmods add skills/dojogenesis/mcp/workspace-navigationWrote 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/dojogenesis/mcp/workspace-navigation)<a href="https://agentmods.dev/skills/dojogenesis/mcp/workspace-navigation"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/workspace-navigation/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/dojogenesis/mcp/workspace-navigation"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/workspace-navigation.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.00041 | $0.04077 |
| Opus 5.5 | $0.00016 | $0.01631 |
| Sonnet 5.5 | $0.00008 | $0.00815 |
| Haiku 4.5 | $0.00004 | $0.00408 |
Grade A, and why
workspace-navigation 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.
How it starts
The opening of the file, as written. The whole thing — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Workspace Navigator Skill
Version: 1.2 Created: 2026-02-11 Author: Tres Pies Design Purpose: Efficiently navigate and interact with shared agent workspaces and discussion rooms
I. Philosophy
This skill encodes best practices for working in shared agent workspaces—structured repositories where multiple agents collaborate, think together, and build shared context. It provides patterns for reading, writing, and organizing content in a way that maximizes clarity, minimizes token waste, and enables effective collaboration.
Philosophy: A shared workspace is not a file dump—it's a thinking room. Structure enables clarity; clarity enables collaboration.
II. When to Use This Skill
- Working in a shared private repository with other agents
- Contributing to or reading from a collaborative discussion space
- Organizing thoughts, specifications, or research in a structured way
- Coordinating work across multiple agents or sessions
- Building shared context without unstructured file chaos
III. Workspace Structure & Workflows
A well-structured agent workspace follows the Planning with Files philosophy and organizes content by purpose, not by time or author.
Standard Directory Structure
workspace/
├── README.md # Workspace overview and navigation guide
├── 00_Active/ # Current work in progress
│ ├── discussions/ # Active discussions and threads
│ ├── drafts/ # Work in progress (not final)
│ ├── decisions/ # Decisions made (with rationale)
│ └── handoffs/ # Pending handoffs between agents
├── 01_Specifications/ # Finalized specs and designs
│ ├── architecture/ # System architecture docs
│ ├── features/ # Feature specifications
│ └── protocols/ # Protocols and standards
├── 02_Research/ # Research findings and synthesis
│ ├── deep-dives/ # Deep research on specific topics
│ ├── landscape-scans/ # Wide research across domains
│ └── references/ # External sources and citations
├── 03_Memory/ # Shared memory and knowledge base
│ ├── seeds/ # Reusable patterns and insights
│ ├── learnings/ # Lessons learned
│ └── context/ # Shared context for continuity
├── 04_Artifacts/ # Generated artifacts and outputs
│ ├── code/ # Code examples or prototypes
│ ├── diagrams/ # Visual artifacts
│ └── documents/ # Final documents
└── 05_Archive/ # Completed or deprecated work
├── by-date/ # Time-based archive
└── by-topic/ # Topic-based archive
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 · 604 lines · 41 tokens per session scan A 8cfc7d5bdf9c
workspace-navigation is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 4,077 once invoked, about $0.0002 per session on Opus 5.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
miro-workflow
Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…
miro-boards
Create and manage Miro board content including stickies, shapes, connectors, diagrams, and mindmaps. Use for whiteboard collaboration, sprint planning, retrospectives, and brainstorming.
scrumboy-board-operator
Operate Scrumboy projects and boards through MCP or Agoragentic APIs. Use when an agent needs to inspect board state, plan sprint work, create todos, move cards, manage tags, or summarize project health.
productplan-pm
Generates comprehensive workflows for product managers to manage roadmaps, OKRs, ideas, and launches in ProductPlan. Use when doing day-to-day product management work, updating feature timelines, tracking objectives, or triaging customer feedback.
productplan-workflows
Generates step-by-step workflows for managing ProductPlan roadmaps, OKRs, ideas, and launches via MCP server tools. Use when working with ProductPlan data, planning features, tracking objectives, or coordinating product launches.
productplan-customer-facing
Generates customer-ready roadmap views and launch timelines from ProductPlan for Sales and Customer Success teams. Use when preparing for customer calls, sharing product direction, or answering "when will feature X ship?" questions.