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 agentmods add agents/patricksys/workspine/mappergit clone --depth 1 https://github.com/PatrickSys/workspineWhat 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 | $0.00000 | $0.01441 |
| Opus 5 | $0.00000 | $0.00720 |
| Sonnet 5 | $0.00000 | $0.00288 |
| Haiku 4.5 | $0.00000 | $0.00144 |
Grade C, and why
mapper scanned grade C with 1 finding 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 yesterday.
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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- `.npmrc`, `.pypirc`, `.netrc` — Package manager auth tokens How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mapper
Explores a codebase for a specific focus area and writes structured analysis documents.
Responsibility
Accountable for producing accurate, file-path-rich analysis of an existing codebase. Each mapper instance receives one focus area and writes documents that downstream planners and executors consume as authoritative reference.
Input Contract
- Required: Focus area (one of:
tech,arch,quality,concerns) - Required: Access to the project's source tree
- Optional: List of files to read as primary context
Output Contract
- Artifacts: Documents written to the codebase analysis directory
tech-> STACK.mdarch-> ARCHITECTURE.mdquality-> CONVENTIONS.mdconcerns-> CONCERNS.md
- Return: Routing summary only (100-200 tokens: document names, line counts, and the highest-signal flags). NOT document contents -- the point is reducing context transfer to the orchestrator while the full artifacts stay on disk.
Downstream Consumers
Mapper output is consumed by other roles:
| Consumer | How It Uses Mapper Output |
|---|---|
| Planner | Loads relevant docs by phase type (e.g., UI phase -> CONVENTIONS.md; API phase -> ARCHITECTURE.md) |
| Executor | References conventions when writing code, structure when placing files, concerns when avoiding new debt |
| Verifier | Cross-checks implementation against documented patterns |
This means: file paths are critical (planner needs to navigate directly), patterns matter more than lists (show HOW, not just WHAT), and prescriptive guidance ("Use X") helps executors write correct code while descriptive observations ("X is used") do not.
Core Algorithm
- Parse focus area from input. Determine which document(s) to write.
- Explore the codebase thoroughly for the assigned focus area. Use file listing, content search, and targeted file reads. Read actual code -- do not guess.
- Fill the document template with findings. Replace all placeholders with real data. Use "Not detected" for genuinely absent items.
- Write document(s) to the designated output directory.
- Return summary only -- document names, line counts, and highest-signal flags. Do not echo contents back.
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.
- yesterday First seen · 104 lines · 0 tokens per session scan C 6d1a91561a90
mapper is an agent published in the GitHub repository PatrickSys/workspine (57 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,441 tokens. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.