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 CoWork-OS/CoWork-OS --skill project-structuregit clone --depth 1 https://github.com/CoWork-OS/CoWork-OSWrote 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/cowork-os/cowork-os/project-structure)<a href="https://agentmods.dev/skills/cowork-os/cowork-os/project-structure"><img src="https://agentmods.dev/badge/skills/cowork-os/cowork-os/project-structure/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/cowork-os/cowork-os/project-structure"><img src="https://agentmods.dev/badge/skills/cowork-os/cowork-os/project-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00009 | $0.00293 |
| Opus 5.5 | $0.00004 | $0.00117 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
project-structure 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.
What it actually says
Project Structure
Purpose
Analyze and explain project architecture
Routing
- Use when: Use when the user asks to analyze and explain project architecture.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Project Structure: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the project-structure skill for this request.
- Help me with project structure.
- Use when the user asks to analyze and explain project architecture.
- Project Structure: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use project-structure for unrelated requests.
- This request is outside project structure scope.
- This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
- Current runtime prompt length: 563 characters.
- Runtime prompt is defined directly in
../project-structure.json.
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 Changed 2ff1a7ca12f8
- 1mo ago First seen · 42 lines · 9 tokens per session scan A bcf8e038eae0
project-structure is a skill published in the GitHub repository CoWork-OS/CoWork-OS (511 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 293 once invoked, about $0.0000 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-03.
Other skills, from other repositories
research-paper-writing
Pipeline for ML/AI research papers — lit review to LaTeX submission.
github-pr-workflow
Pull request lifecycle: create, review, merge, manage (gh CLI).
planning
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. If workflowbuildercreatetasks is not visible, load it via loadtool (search "create tasks"). Do NOT use for new one-off workflows…
github-review
Review a GitHub pull request by collecting GitHub context, applying evidence-backed review rules, and optionally publishing one review.
code-health-audit
Audit code-health and technical-debt signals with evidence, rank proportionate interventions from focused cleanup to broad coordinated refactors, and draft implementation-ready plans without granting implementation permission.
ghx
Guidance for safe, reliable GitHub CLI workflows across issues, pull requests, and reviews.