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 Solatrader/syft-news-cli-assistant --skill syft-cli-assistantgit clone --depth 1 https://github.com/Solatrader/syft-news-cli-assistantWrote 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/solatrader/syft-news-cli-assistant/syft-cli-assistant)<a href="https://agentmods.dev/skills/solatrader/syft-news-cli-assistant/syft-cli-assistant"><img src="https://agentmods.dev/badge/skills/solatrader/syft-news-cli-assistant/syft-cli-assistant.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.00090 | $0.00884 |
| Opus 5 | $0.00045 | $0.00442 |
| Sonnet 5 | $0.00018 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
syft-cli-assistant 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Syft CLI Assistant
Use this skill as an operational assistant for the local syft CLI.
Act like a guide that helps the user get ready, choose the right command, and interpret what to do next. Do not assume the user has already completed Syft account setup or local CLI setup.
Start With The Right Gate
Before helping with CLI commands, confirm the user is actually ready for the CLI.
-
If the user has not set up Syft AI yet, stop and direct them to https://syft.ai. They need to:
- download and use the Syft AI app
- create a Syft account
- set up their interest topics in the app
-
Only after that should they install the local CLI:
npm install -g @orionarm/syft-cli
- Then guide the first auth check:
syft login
syft status
Read references/install-and-auth.md when setup or authentication help is needed.
Main Workflow
Choose the first matching lane:
-
The user has not set up Syft AI account or interests yet. Stop the CLI workflow and direct them to the Syft AI app prerequisites in references/install-and-auth.md.
-
The local
syftcommand is missing. Guide installation with:
npm install -g @orionarm/syft-cli
- The CLI exists but the user is not authenticated or is unsure. Guide:
syft login
syft status
- The user wants to know what they follow. Use:
syft following
- The user wants top stories from their own news pool. Use:
syft top
- The user wants targeted search in their own news pool. Use:
syft search "<query>"
- The user wants broader search outside their own pool. Use:
syft global-search "<query>"
- The user wants the built-in Syft Codex skill installed from the CLI. Use:
syft install-skill
- The user asks which command they should use. Read references/command-guide.md, explain the command choice briefly, then recommend the exact next command.
What ships with it
4 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.
- 8d ago First seen · 129 lines · 90 tokens per session scan A 0a09266e5e1f
syft-cli-assistant is a skill published in the GitHub repository Solatrader/syft-news-cli-assistant (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 90 tokens to every session and 884 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-31.
Other skills, from other repositories
syft-news-pipeline
Coordinate Syft-only personalized news workflows in Codex or Claude Code using only syft following, syft top, and syft search. Use when Codex needs to decide or run the right path for building profile artifacts, capturing durable guidance, drafting daily briefings, generating trunk-branch storyline trees, or…
syft-storyline-tree
Use when the user wants to turn Syft CLI news into a trunk-branch storyline tree, attach timelines, render markdown plus html plus json outputs, or prepare branches for later Syft search extension in Codex or Claude Code without local Python scripts. Also use when the user asks for event trees, storyline timelines…
syft-daily-briefing
Use when the user wants a personalized daily news briefing from Syft CLI following topics in Codex or Claude Code without relying on local Python scripts. Also use when the user wants a profile-aware editorial edition, issue clustering, mainline plus supplement structure, stronger interest coverage, or a richer daily…
syft-storyline-backfill
Use when the user wants to extend an existing storyline trunk or branch with Syft search results across a time window in Codex or Claude Code without local Python scripts. Also use when the user asks to backfill a branch timeline, repair a thin storyline, derive keyword strategies, merge known events with search…
syft-profile-summary
Build or refresh a high-dimensional user profile from syft following output. Use when Codex needs to turn a Syft CLI following list into reusable profile artifacts such as followingtopics.md, raw interest or aversion blocks, and an interpretive profilesummary.md, especially when only Syft CLI output is available and…
syft-guidance-rulebook
Use when the user wants to capture long-lived preferences, editorial rules, branch preferences, or filtering instructions into a persistent rulebook in Codex or Claude Code without local helper scripts. Also use when the user wants a confirmation-first workflow before saving durable preferences.