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 atman-33/workhub --skill shared-spacegit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/shared-space)<a href="https://agentmods.dev/skills/atman-33/workhub/shared-space"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/shared-space/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/atman-33/workhub/shared-space"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/shared-space.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.00094 | $0.01818 |
| Opus 5.5 | $0.00038 | $0.00727 |
| Sonnet 5.5 | $0.00019 | $0.00364 |
| Haiku 4.5 | $0.00009 | $0.00182 |
Grade A, and why
shared-space 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 21d 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.
shared-space — the team knowledge bases outside the vault
A vault project's notes are for the owner and their agents. A team keeps its own material somewhere else — a network drive, a Google Drive or SharePoint folder — organised by conventions nobody wrote down anywhere the vault can see.
This skill records those places against a project, and uses what it recorded to say where something belongs. It has two modes.
| Mode | What it does |
|---|---|
survey <project> <location> |
Read the place, work out how it is organised, and write projects/NNNN-<slug>/shared/<name>.md |
place <note> |
Say where a vault note belongs in the project's shared spaces, and prepare the copy |
The app's Projects tab lists what shared/ holds and offers a prompt that
launches survey mode; nothing about these notes is written by the app itself.
Source of truth. The format spec is .claude/rules/shared-space.md in the vault; it loads when you read a shared-space note. The sections below are a working summary for surveying, and the rule wins where they differ.
What is worth recording
The rules, not the folder tree. Naming conventions, which kind of document goes where, who owns what, what the review or approval step is. A listing of every folder is stale within weeks and nobody reads it; keep the structure to the parts that orient a reader.
A place with no rules to record is just a link, and belongs in the project's
links.md instead. Do not create a shared-space note for one.
The note
projects/NNNN-<slug>/shared/<name>.md. One file is one place; the folder is the
registry, so nothing lists these notes in _index.md. <name> is English
kebab-case, like every other folder name in the vault.
---
type: shared-space
title: Design team share
kind: network-drive # network-drive | google-drive | onedrive | sharepoint | other
location: //fileserver/design/projectX
access: mapped to Z:, needs VPN
direction: read-only # read-only | export-ok
surveyed: 2026-09-05
---
## Structure
- `01_仕様/` — specifications, one folder per release
- `02_議事録/` — meeting minutes, `YYYY-MM-DD_<topic>.md`
- `99_archive/` — anything superseded
## Rules
- A file name starts with the date in `YYYYMMDD` (stated: `運用ルール.md`)
- Specifications are Word, minutes are Markdown (inferred)
- The release folder is created by the PM, not by contributors (stated)
## Placement
- Task deliverables about the UI → `01_仕様/<release>/`
- Meeting notes → `02_議事録/`
## Memo
The owner's own notes. Neither the app nor this skill rewrites this section.
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.
- 21d ago Changed · +3 lines 85e6438c3224
- 1mo ago Changed · +4 tokens per session 03d563517bf0
- 1mo ago First seen · 158 lines · 90 tokens per session scan A 60068e449039
shared-space is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 94 tokens to every session and 1,818 once invoked, about $0.0004 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-09-06.
Other skills, from other repositories
expo-launchpad-status
Show the current expo-launchpad pipeline state — phase, round, next role, pause reason — read-only.
tasknotes
This skill should be used when the user asks to 'create a task', 'add a TODO', 'plan a sprint', 'organize tasks', 'track time', 'setup Kanban', 'create task from code', 'sync tasks with sprint', 'pomodoro session', 'start pomodoro', 'time estimate', or mentions TaskNotes, task management, or project planning in…
issue-hygiene
How to write an issue somebody can act on, how to triage a pile of them, and the label vocabulary that stays useful. Use when filing, triaging, labelling, closing or linking issues.
aetox-slice
Decomposes a technical specification or plan into vertical tracer-bullet tickets. Calculates directed dependency graphs (DAG), schedules prefactoring first, applies expand-contract sequencing for wide refactors, quizzes the user on ticket granularity, and emits atomic per-ticket files sized for optimal agent context…
project-consolidation
Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. Apps-arena, GitHub-loom), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project…
roadmap-update
Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…