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 commands/datasift-ty-personal/siftstack/sift-workflowgit clone --depth 1 https://github.com/DataSift-Ty-Personal/SiftStackWhat 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.00006 | $0.00520 |
| Opus 5 | $0.00003 | $0.00260 |
| Sonnet 5 | $0.00001 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
sift-workflow 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 2d 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
The user wants a walkthrough for a specific Sift operation. Follow this process:
-
Read the skill file at
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/SKILL.mdto load the domain routing table. -
Based on the user's description ($ARGUMENTS), identify what they want to do and read the appropriate reference(s):
- Sequences:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/sequences-core.md - Lead management:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/lead-management-sequences.md - Acquisitions:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/acquisitions-sequences.md - Board workflows:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/board-workflows.md - Drip campaigns:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/drip-campaigns.md - Events/tasks:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/events-and-tasks.md - Filter presets:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/filter-configurations.md - General operations:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/general-operations.md - Troubleshooting:
${CLAUDE_PLUGIN_ROOT}/skills/sift-operations/references/troubleshooting.md
If the ask is about finding, vetting, or contacting contractors/vendors for a market (an operations task outside Sift), route to the vendor-directory-builder and contractor-call-sheet skills instead of the Sift references.
- Sequences:
-
Provide the response in hybrid format: a. Concept Brief (2-4 sentences) — explain what this feature is and why it matters b. Step-by-Step Walkthrough — numbered, click-by-click instructions with exact menu locations and field names c. Configuration Details — tables showing exact settings d. Best Practices — 2-3 actionable tips e. Related Features — mention connected features they might also want to set up
-
If the walkthrough involves multiple interconnected features (e.g., setting up a full lead management system), generate a comprehensive reference document saved to the workspace folder.
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.
- 2d ago First seen · 32 lines · 6 tokens per session scan A c19a6cb26add
sift-workflow is a command published in the GitHub repository DataSift-Ty-Personal/SiftStack (21 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 520 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.