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 memi-design/design-skills --skill notion-syncgit clone --depth 1 https://github.com/memi-design/design-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/memi-design/design-skills/notion-sync)<a href="https://agentmods.dev/skills/memi-design/design-skills/notion-sync"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/notion-sync/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/memi-design/design-skills/notion-sync"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/notion-sync.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.00029 | $0.00116 |
| Opus 5 | $0.00015 | $0.00058 |
| Sonnet 5 | $0.00006 | $0.00023 |
| Haiku 4.5 | $0.00003 | $0.00012 |
Grade A, and why
notion-sync 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 9d 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
Sync with Notion
Read the Notion integration guide. Confirm the connected workspace, target database, properties, source of truth, and write scope before mutation. Map fields explicitly, validate external data, preserve stable IDs, and make retries idempotent. Never expose integration secrets. End with counts, skipped records, conflicts, and links or identifiers for the updated records.
What ships with it
2 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.
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.
- 9d ago First seen · 9 lines · 29 tokens per session scan A d63adad5f118
notion-sync is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 116 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
execute-round
Use when a planned round handoff exists and needs to be implemented end-to-end via the 4-commit chain (entry-admin → BA design → dev body with inline CR + SE → state refresh + self-audit). Dispatches ba-designer / developer / cr-reviewer / se-contract sequentially.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
post-issue-comment
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
ticket-craft
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.