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/xyruscode/ai-sync/daily-reportnpx skills add XyrusCode/ai-sync --skill daily-reportgit clone --depth 1 https://github.com/XyrusCode/ai-syncWhat 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.00041 | $0.02800 |
| Opus 5 | $0.00020 | $0.01400 |
| Sonnet 5 | $0.00008 | $0.00560 |
| Haiku 4.5 | $0.00004 | $0.00280 |
Grade A, and why
daily-report 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 yesterday.
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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Intelligence Brief Generator
Generate a professional daily report analyzing global events, macro trends, industrial developments, and policy shifts.
Workflow
Step 0: User Preference Discovery
Ask user if they have specific focus areas before generating:
"将为您生成通用版日报（覆盖全球政经、产业、科技）。如需定制，请告诉我关注的领域（如科技/消费/文化等）。"
| 偏好类型 | 示例 | 处理方式 |
|---|---|---|
| 无偏好（默认） | - | 通用5领域模板 |
| 科技产业 | 半导体、AI、新能源 | 产业章节深入展开 |
| 宏观政经 | 中美、关税、货币政策 | 前置为"今日主线"深度分析 |
| 消费生活 | 品牌动态、零售、美食、旅行 | 增加消费趋势板块 |
| 文化娱乐 | 影视、音乐、艺术、出版 | 替换默认模板中的产业部分 |
Step 1: Intelligence Gathering
Search for today's critical developments across these domains:
A. Geopolitics & Security
- Military conflicts, territorial disputes, sanctions
- Diplomatic breakthroughs or breakdowns
- Supply chain disruptions (shipping routes, key chokepoints)
B. China Macro & Policy
- National People's Congress, policy meetings
- GDP targets, fiscal/monetary policy signals
- Regulatory changes affecting key sectors
C. Global Monetary Policy
- Central bank decisions (Fed, ECB, BOJ, PBOC)
- Inflation data, employment reports
- Interest rate expectations and market pricing
D. Industrial & Supply Chain
- Semiconductor, EV, battery, renewable energy developments
- Trade flows, inventory levels, capacity utilization
- Technology breakthroughs or bottlenecks
E. Tech Governance & Markets
- AI regulation, data privacy, antitrust actions
- Major tech earnings, M&A, strategic shifts
- Cryptocurrency/digital asset regulatory developments
Search Strategy:
- Use WebSearch with site filters:
site:bloomberg.com OR site:reuters.com OR site:ft.com OR site:wsj.com - Check official sources: government portals, central bank statements
- Cross-verify with at least 2 independent sources for major claims
Step 2: Content Selection Criteria
Apply two layers of filtering:
Layer 1: User Preferences (from Step 0)
- Prioritize stories matching user's specified industries/regions/themes
- If user wants "半导体", ensure at least one deep-dive semiconductor story
- If user wants "中美", weight US-China related news higher in selection
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.
- yesterday First seen · 337 lines · 41 tokens per session scan A 1ec0668d050c
daily-report is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 2,800 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…