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 agentmods add skills/sifter-ai/sifter/sdd-remotenpx skills add sifter-ai/sifter --skill sdd-remotegit clone --depth 1 https://github.com/sifter-ai/sifterWrote 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/sifter-ai/sifter/sdd-remote)<a href="https://agentmods.dev/skills/sifter-ai/sifter/sdd-remote"><img src="https://agentmods.dev/badge/skills/sifter-ai/sifter/sdd-remote.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 | $0.00101 | $0.00931 |
| Opus 5 | $0.00051 | $0.00465 |
| Sonnet 5 | $0.00020 | $0.00186 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
sdd-remote 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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Remote — Pull, Enrich, Push
Purpose
Synchronize local SDD docs with remote updates (from the SDD Flow server), enrich draft content, and publish the enriched result to remote in active states.
This skill also applies when a remote worker job is dispatched from SDD Flow — the worker runs these same workflows on behalf of the user.
Detection
This workflow applies when:
.sdd/config.yamlexists in the project root with aremote:section configured- The user asks to update local state from remote, pull pending CRs/bugs/docs, enrich drafts, or push pending remote updates
- A remote worker job prompt instructs you to follow this workflow
Before any pull/push operation, check remote configuration with sdd remote status.
Workflows
Enrich workflow — Change Request
Follow this sequence to enrich a draft CR:
- Pull remote drafts:
sdd pull --crs-only
- Generate the draft TODO list:
sdd drafts
-
Enrich the draft with technical details, acceptance criteria, edge cases, and any relevant information from the project documentation and comments.
-
Transition the enriched CR from
drafttopending:
sdd mark-drafts-enriched
- Push the enriched content:
sdd push
Enrich workflow — Document
Follow this sequence to enrich a document (e.g. a feature spec):
- Pull remote drafts:
sdd pull --docs-only
-
Locate the document file in
product/orsystem/and update its content with the enriched version. -
Push the enriched content:
sdd push
If the document was in draft status, it transitions to new on the server.
Sync workflow — Project-level
Full project sync when the user asks for "the latest" or "pull everything and implement":
- Pull the latest specs:
sdd pull
-
Run the
sddskill — it handles the full loop: open bugs, pending CRs, documentation sync, code implementation, mark-synced, and commit. -
Push the local updates:
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.
- 4d ago First seen · 130 lines · 101 tokens per session scan A 5164c331ab5f
sdd-remote is a skill published in the GitHub repository sifter-ai/sifter (55 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 931 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…
sales-ops
Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks…