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 bjorn-ingmanson/thefroject-plugins --skill enrich-workspacegit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/enrich-workspace)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/enrich-workspace"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/enrich-workspace/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/bjorn-ingmanson/thefroject-plugins/enrich-workspace"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/enrich-workspace.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.00071 | $0.01316 |
| Opus 5 | $0.00036 | $0.00658 |
| Sonnet 5 | $0.00014 | $0.00263 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
enrich-workspace 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 10d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enrich Workspace
Find the gaps that make Claude generic, then ask the user 1-2 questions per gap to fill them. Quick session, real impact. The default state of a hatched workspace is "templated" — this skill makes it personal.
Gather Context First
- Read
.froject.jsonfor workspace type, role, and hatched status - List every file in
context/,notes/,reference/(or workspace-equivalents) - Read
CLAUDE.mdto understand the workspace structure expected by this project type - Identify the user's role and tools — this shapes which gaps matter most
The Gap Scan
Score each context source against four signals. A "gap" is anything that scores poorly on at least two.
Signal 1 — Placeholder text
Flag files containing:
[your audience],[describe your...],[fill in],[TODO],[FIXME],<your-name>,xxx- "Lorem ipsum" or obvious filler
- Section headers with no content underneath
- Default Froject template phrasing that wasn't customized
Signal 2 — Thinness
A context file Claude reads every session needs density. Flag files where:
- Body is under 10 lines (excluding headers and metadata)
- Sections are present but only have 1-2 lines of generic copy
- The whole file reads like a description from a template, not from the user
Signal 3 — Missing for the role
Each project type expects certain context files. Cross-reference what's present vs. what the role needs:
| Role | Expected context |
|---|---|
| Marketing | brand voice, target audience, ICP, key messages, content guidelines |
| Sales | ICP, deal stages, objection patterns, key competitors, current pipeline |
| Product | product vision, roadmap, key personas, success metrics, design principles |
| Customer success | onboarding playbook, health-score logic, expansion patterns, churn signals |
| People & Culture | values, hiring rubric, performance principles, company history |
| Software | architecture, conventions, tooling, deployment, key tradeoffs |
| Operations | processes, vendor list, decision rights, escalation paths |
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.
- 10d ago First seen · 132 lines · 71 tokens per session scan A 8aae4001c318
enrich-workspace is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,316 once invoked, about $0.0004 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.