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/robinsadeghpour/content-workflow/pulsenpx skills add robinsadeghpour/content-workflow --skill pulsegit clone --depth 1 https://github.com/robinsadeghpour/content-workflowWrote 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/robinsadeghpour/content-workflow/pulse)<a href="https://agentmods.dev/skills/robinsadeghpour/content-workflow/pulse"><img src="https://agentmods.dev/badge/skills/robinsadeghpour/content-workflow/pulse.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.00114 | $0.01255 |
| Opus 5 | $0.00057 | $0.00628 |
| Sonnet 5 | $0.00023 | $0.00251 |
| Haiku 4.5 | $0.00011 | $0.00126 |
Grade A, and why
pulse 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pulse -- Content Discovery Pipeline
Automated daily discovery that keeps Robin's content backlog stocked with trending AI/tech ideas -- no manual searching required.
Prerequisites
Ensure .env contains:
APIFY_TOKEN-- required for TikTok and X scrapersSUPADATA_API_KEY-- required for transcript extractionANTHROPIC_API_KEY-- required for content generation phases (not used by pulse itself)
Running the Pulse
Step 1: Ensure DB is initialized with transcript column
node scripts/init-db.js
Step 2: Run the full pulse
node scripts/pulse.js
This will:
- Scrape YouTube (via yt-search), TikTok (via Apify
clockworks/tiktok-scraper), X/Twitter (via Apifyapidojo/tweet-scraper), and Anthropic changelogs (via Cheerio) - Score each idea by recency + engagement (no Claude API calls -- pure numeric formula)
- Deduplicate against existing
data/content.dbentries using SHA-256 URL hashes - Eagerly fetch transcripts for all YouTube and TikTok ideas via Supadata
- Insert new ideas into
data/content.db(ideas table, status='new') - Generate a dated markdown review file at
data/review/YYYY-MM-DD.md
Source failures are logged and skipped -- the pulse continues even if one source is down.
Step 3: Read and display the review file
After the pulse completes, read the review file to present a summary:
cat data/review/$(date +%Y-%m-%d).md
Present the top ideas from the review file to Robin with their scores, sources, and content angle suggestions.
Expected Output
[PULSE] 2026-04-09T06:00:00.000Z -- pulse started
[PULSE] youtube: 12 ideas found
[PULSE] tiktok: 8 ideas found
[PULSE] x: 15 ideas found
[PULSE] changelog: 3 ideas found
[PULSE] 18 new ideas (20 duplicates filtered)
[TRANSCRIPT] Fetching transcripts for 10 video ideas...
[TRANSCRIPT] 8/10 transcripts fetched
[PULSE] Inserted 18 ideas into data/content.db
[REVIEW] Review file written: data/review/2026-04-09.md
[PULSE] Done. 18 ideas written to DB. Review file generated.
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 · 153 lines · 114 tokens per session scan A 62d894152d55
pulse is a skill published in the GitHub repository robinsadeghpour/content-workflow (55 stars, last pushed 3mo ago), licensed MIT. It adds 114 tokens to every session and 1,255 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…