Borrowing it
Nothing to install: this file belongs to shashankrai1983/fb-ads-automation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shashankrai1983/fb-ads-automation/main/.claude/commands/fb-ads/daily-check.mdgit clone --depth 1 https://github.com/shashankrai1983/fb-ads-automationWrote 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/commands/shashankrai1983/fb-ads-automation/daily-check)<a href="https://agentmods.dev/commands/shashankrai1983/fb-ads-automation/daily-check"><img src="https://agentmods.dev/badge/commands/shashankrai1983/fb-ads-automation/daily-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/shashankrai1983/fb-ads-automation/daily-check"><img src="https://agentmods.dev/badge/commands/shashankrai1983/fb-ads-automation/daily-check.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00289 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
daily-check 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 10d 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
Run a daily health check on the Facebook Ads account.
Steps
-
Get today's date and call
get_account_spending_summarywithdate_preset=todayto see today's spending status, then alsodate_preset=yesterdayfor comparison. -
Call
get_all_campaign_insightswithdate_preset=last_7dandstatus_filter=ACTIVEto get all active campaign performance. -
For each active campaign with significant spend (top 5 by spend), call
get_creative_fatigue_reportwithdays=7to check for creative fatigue. -
Read
knowledge/playbook.mdfor current threshold values. Cross-reference results against the Red Flag Thresholds table and Decision Frameworks. -
Present a structured daily health report:
## Daily Health Check — [Date]
### Account Status
- Today's spend: $X (vs $Y yesterday)
- Active campaigns: N
- Total impressions: N
### Red Flags (action needed)
[List any critical/warning flags with specific campaign names]
### Watch List (monitoring)
[Items approaching thresholds but not yet flagged]
### Recommended Actions
[Numbered list of specific actions, each requiring user confirmation]
- If any actions are recommended, list them clearly and wait for user confirmation before taking any write actions.
Do NOT execute any write operations without explicit user approval.
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.
- 10d ago First seen · 36 lines · 0 tokens per session scan A 18f60315a20c
daily-check is a command published in the GitHub repository shashankrai1983/fb-ads-automation (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 289 tokens. 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-09-01.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.