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-daily-ritualsgit 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-daily-rituals)<a href="https://agentmods.dev/skills/synthesisengineering/synthesis-skills/synthesis-daily-rituals"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-daily-rituals/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-daily-rituals"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-daily-rituals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 Rogue Agent · line 49 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.
- medium Rogue Agent · line 343 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.
- low Excessive Agency · line 444 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00091 | $0.14811 |
| Opus 5 | $0.00046 | $0.07405 |
| Sonnet 5 | $0.00018 | $0.02962 |
| Haiku 4.5 | $0.00009 | $0.01481 |
Grade A, and why
synthesis-daily-rituals 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Rituals — Global Checklists
Standard day-start and day-end rituals for synthesis engineering projects. These are the global (per-person) checklists. Each project may have a project-specific supplement that extends these with channel-specific sync, repo-specific checks, and stakeholder-specific communications.
Version history, the rationale behind each rule, and the incidents that produced them: references/version-history.md. The distributed desk/worker contract: references/ritual-worker-contract.md. Sync watermarks: references/sync-watermarks.md. Daily plan format and vocabulary: references/plan-format.md. Draft grounding and formatting in full: references/draft-grounding.md. On a machine provisioned by the gated release, every <…-root> placeholder below resolves under ~/.synthesis/plugins/synthesis-skills/current/skills/; never pin a versioned cache path — the Step 1 parity check fails when that pointer is missing or stale.
Configuration
These values are user-specific. Update them for your environment.
| Setting | Value | Description |
|---|---|---|
daily_plans_path |
daily-plans/ |
Where daily action plans are saved (person-scoped, in the personal ai-knowledge repo) |
transcripts_path_in_private |
transcripts/ |
Relative subpath within each workspace-private repo. Workspace subdirs are NOT part of the path — they're implicit in the repo name (ADR-018) |
personal_repo |
~/workspaces/<person>/ai-knowledge-<person> |
Absolute path to personal root. Daily plans, lessons, cross-workspace projects live here |
workspace_private_repo_pattern |
~/workspaces/{workspace}/ai-knowledge-{workspace}-rajiv-private |
Path pattern for workspace-private repos (Type 3 content) |
index_yaml_path |
projects/index.yaml |
Relative to personal_repo; project index file to update last_session |
lessons_path |
lessons/ |
Relative to personal_repo; where reusable lessons are stored (ADR-017) |
downloads_path |
~/Downloads/ |
Where meeting transcripts are initially downloaded |
alert_sound |
/System/Library/Sounds/Glass.aiff |
macOS sound file for autonomous work alerts |
slack_auth_command |
tool-specific Slack auth flow | Command or UI flow to re-authenticate Slack for the current agent |
What ships with it
29 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.
- agents/openai.yaml 256 B
- references/decay-sweep.md 5.7 KB
- references/draft-grounding.md 12 KB
- references/plan-format.md 11 KB
- references/ritual-worker-contract.md 13 KB
- references/sync-watermarks.md 7.3 KB
- references/version-history.md 58 KB
- scripts/com.synthesis.day-end-nudge.plist 1.2 KB
- scripts/day-end 3.8 KB
- scripts/day-end-nudge.sh 2.5 KB runs code
- scripts/decay_sweep.py 12 KB runs code
- scripts/fixtures/decay-sweep/plans/2026-08-01.md 142 B
- scripts/fixtures/decay-sweep/plans/2026-09-04.md 80 B
- scripts/fixtures/decay-sweep/plans/2026-09-08.md 198 B
- scripts/fixtures/decay-sweep/plans/notes.md 63 B
- scripts/gchat_preflight.py 10 KB runs code
- scripts/install_day_end.py 5.0 KB runs code
- scripts/portfolio_review.py 8.9 KB runs code
- scripts/pr_queue_scan.py 16 KB runs code
- scripts/ritual_state.py 29 KB runs code
- scripts/sync_watermark.py 24 KB runs code
- scripts/test_decay_sweep.py 8.1 KB runs code
- scripts/test_gchat_preflight.py 7.9 KB runs code
- scripts/test_install_day_end.py 11 KB runs code
- scripts/test_portfolio_review.py 4.8 KB runs code
- scripts/test_pr_queue_scan.py 22 KB runs code
- scripts/test_skill_documents.py 6.2 KB runs code
- scripts/test_sync_watermark.py 21 KB runs code
- scripts/test_version_record.py 3.2 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 e372d418b0da
- 2d ago Changed fbe0ddf68c1a
- 4d ago Changed · +2 lines 406569b3a108
- 5d ago Changed · +1 lines eb7ba637607a
- 8d ago Changed · -842 lines e74d3c7a86dc
- 12d ago First seen · 1,289 lines · 91 tokens per session scan A f22ce416cf17
synthesis-daily-rituals is a skill published in the GitHub repository synthesisengineering/synthesis-skills (19 stars, last pushed today), licensed Apache-2.0. It adds 91 tokens to every session and 14,811 once invoked, about $0.0005 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
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…