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 synthesisengineering/synthesis-skills --skill synthesis-project-managementgit clone --depth 1 https://github.com/synthesisengineering/synthesis-skillsWrote 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/synthesisengineering/synthesis-skills/synthesis-project-management)<a href="https://agentmods.dev/skills/synthesisengineering/synthesis-skills/synthesis-project-management"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-project-management/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/synthesisengineering/synthesis-skills/synthesis-project-management"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-project-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 462 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 210 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00068 | $0.06759 |
| Opus 5 | $0.00034 | $0.03379 |
| Sonnet 5 | $0.00014 | $0.01352 |
| Haiku 4.5 | $0.00007 | $0.00676 |
Grade A, and why
synthesis-project-management 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 today.
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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesis Project Management System
A lightweight project management system designed for human-agent collaboration. Optimized for context preservation across conversation sessions and context compaction events.
Configuration
These values are user-specific. Update them for your environment.
| Setting | Value | Description |
|---|---|---|
ai_knowledge_workspace |
ai-knowledge-{workspace} |
Root directory for your ai-knowledge repo (e.g., ai-knowledge-rajiv) |
projects_path |
projects/ |
Directory within the workspace for all project folders |
index_file |
projects/index.yaml |
Single index file for all projects |
lessons_path |
lessons/ |
Cross-project lessons and patterns directory |
Design Principles
- Discoverability over documentation — Agents can search/grep; humans need quick orientation. Prefer consistent naming conventions over maintained indexes.
- Convention over configuration — Consistent structure means less cognitive load. When everything follows the same pattern, both humans and agents know where to look.
- Single source of truth — No duplicate indexes to maintain. Files should be self-describing through front matter and naming conventions.
- Self-describing files — Date prefixes, status in index.yaml, front matter metadata. No separate documentation that can get stale.
- Agents do the work — Templates are obsolete. To create something new, examine an existing example and adapt it. Agents excel at this.
- Coordinate before concurrent writes — Separate root sessions share a session registry and message board outside the repositories they edit. Every session reads it, registers its project, claims its write areas, and records its isolated worktree before editing.
- One context owner per project — Parallel sessions may contribute to one project, but only one session writes canonical project context. Other sessions write isolated contribution artifacts for deterministic reconciliation.
What ships with it
32 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- acceptance-suite.yaml 6.3 KB
- agents/openai.yaml 227 B
- references/active-sessions-template.md 2.3 KB
- references/checkpoint-closure-recovery.md 3.8 KB
- references/codex-dispatch.md 1.4 KB
- references/parallel-agent-protocol.md 22 KB
- references/project-state-recovery.md 4.9 KB
- references/records-and-conventions.md 6.1 KB
- references/session-identity.md 6.5 KB
- references/session-words-v1.LICENSE.md 1.3 KB
- references/session-words-v1.txt.zlib.b85 7.7 KB
- scripts/board_inbox.py 8.3 KB runs code
- scripts/codex_dispatch.py 7.1 KB runs code
- scripts/coordination_schema.py 15 KB runs code
- scripts/coordination.py 104 KB runs code
- scripts/handoff.py 9.1 KB runs code
- scripts/peer_addressing.py 35 KB runs code
- scripts/peer_send_gate.py 17 KB runs code
- scripts/plan_reference.py 8.0 KB runs code
- scripts/pointer_lock.py 1.7 KB runs code
- scripts/project_recipient.py 7.7 KB runs code
- scripts/project_state.py 67 KB runs code
- scripts/retire_worktree.py 21 KB runs code
- scripts/test_board_inbox.py 7.0 KB runs code
- scripts/test_checkpoint_observer.py 25 KB runs code
- scripts/test_coordination.py 86 KB runs code
- scripts/test_diagnostic_inbox.py 21 KB runs code
- scripts/test_handoff.py 5.2 KB runs code
- scripts/test_peer_addressing.py 21 KB runs code
- scripts/test_peer_send_gate.py 15 KB runs code
- scripts/test_project_state.py 39 KB runs code
- scripts/test_retire_worktree.py 25 KB runs code
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.
- today Changed · +2 lines 84b3827384b6
- 3d ago Changed · -1 lines 00fd75fdf795
- 4d ago Changed 728819c10d5a
- 5d ago Changed · -1 lines 894b7c2539b1
- 6d ago Changed b42235075e49
- 7d ago Changed · -149 lines b75cd163359c
- 11d ago First seen · 649 lines · 68 tokens per session scan A 4a6cab882549
synthesis-project-management is a skill published in the GitHub repository synthesisengineering/synthesis-skills (18 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 6,759 once invoked, about $0.0003 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.