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 WellApp-ai/Well --skill notion-syncgit clone --depth 1 https://github.com/WellApp-ai/WellWrote 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/wellapp-ai/well/notion-sync)<a href="https://agentmods.dev/skills/wellapp-ai/well/notion-sync"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/notion-sync.svg" alt="Measured on agentmods" 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.00013 | $0.01764 |
| Opus 5 | $0.00006 | $0.00882 |
| Sonnet 5 | $0.00003 | $0.00353 |
| Haiku 4.5 | $0.00001 | $0.00176 |
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 7d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion Sync Skill
Standardize how Notion tasks are updated across all modes.
When to Use
- Push PR mode: update PR link and append plan
- Init mode: update branch name
- Any mode updating task status
- Appending content to task pages
Phases
Phase 1: Retrieve Task Page
Fetch current task state:
API-retrieve-a-page:
page_id: [task-page-id]
Verify the page exists and note current field values.
Phase 2: Update Standard Fields
Update properties based on context:
Available fields:
| Field | Type | When to Update |
|---|---|---|
| Github PR link | url | On PR creation |
| Branch name | rich_text | On branch creation |
| Lifecycle/Status | select | On state changes |
API call:
API-patch-page:
page_id: [task-page-id]
properties:
"Github PR link": { url: "[PR-URL]" }
"Branch name": { rich_text: [{ text: { content: "[branch-name]" }}]}
Phase 3: Append Content (Optional)
If content needs to be added to the page body:
Get existing blocks:
API-get-block-children:
block_id: [page-id]
Append new content:
API-patch-block-children:
block_id: [page-id]
children: [
{
"type": "heading_2",
"heading_2": { "rich_text": [{ "text": { "content": "Implementation Plan" }}]}
},
{
"type": "paragraph",
"paragraph": { "rich_text": [{ "text": { "content": "[plan-content]" }}]}
}
]
Content types to append:
- Implementation plans (from Plan mode)
- PR summaries (from Push PR mode)
- Status updates
Phase 4: Confirm Sync
Verify the update was successful:
API-retrieve-a-page:
page_id: [task-page-id]
Check that updated fields reflect new values.
Phase 5: Session Journal Sync (NEW)
Sync session metrics and decisions to Session Journal database.
When to Run
- After PR is created (via push-pr.mdc)
- On manual "sync session" command
- On session abandon
5.1: Gather Session Data
Collect from session-status skill:
- Duration, loops, rework, waiting, RED count, escalations
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.
- 7d ago First seen · 267 lines · 13 tokens per session scan A a295d9eb44cb
notion-sync is a skill published in the GitHub repository WellApp-ai/Well (340 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,764 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-08-30.
Other skills, from other repositories
turborepo
Skill "turborepo" from ashish7802/awesome-api-skills, covering turborepo skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
c-github
Interact with GitHub using the gh CLI and jq. Manage PRs, issues, repositories, and Actions workflows. Make raw API calls with gh api for anything not covered by built-in commands.
accelo-automation
Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas.
acculynx-automation
Automate Acculynx tasks via Rube MCP (Composio). Always search tools first for current schemas.
aero-workflow-automation
Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas.
affinity-automation
Automate Affinity tasks via Rube MCP (Composio). Always search tools first for current schemas.