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/noontide-co/mainbranch/mb-adsnpx skills add noontide-co/mainbranch --skill mb-adsgit clone --depth 1 https://github.com/noontide-co/mainbranchWhat 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.00136 | $0.05897 |
| Opus 5 | $0.00068 | $0.02949 |
| Sonnet 5 | $0.00027 | $0.01179 |
| Haiku 4.5 | $0.00014 | $0.00590 |
Grade A, and why
mb-ads 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ads Skill
Create ads, generate creative variations, review for compliance, and check ad account performance.
CLI facts first: Find the business repo, run mb status --json --peek,
then use status readiness, drift, integrations, measurement, and ranked actions
before scoring creative depth or asking setup/provider questions.
Shared Workflow Contract
Engine source workflow: workflows/mb-ads/workflow.md. This skill is the
Claude Code shell over that source. Preserve the shared source's fact-first
routing, launch-plan boundaries, provider gates, and read/write rules.
Shared source required mb commands:
mb status --json --peekmb start --jsonmb doctor repair --planmb connect doctor --jsonmb connect planmb launch check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --jsonmb site check "$SITE_REPO" --business-repo "$BUSINESS_REPO" --jsonmb validate --cross-refs --jsonmb checkpoint --plan --json
Shared source required JSON fact paths:
money_pathmoney_path.objects.proof.qualitymoney_path.objects.cta_pathmoney_path.objects.channel_strategymoney_path.objects.active_pushvalidation.file_contractscontent_strategycontent_strategy.overall_statecontent_strategy.simple_entry_pointcontent_strategy.layersranked_actionsupdatereadinessdrift.itemsintegrationsmeasurementmeasurement.availablemeasurement.statemeasurement.facts.expected_eventsmeasurement.facts.instrumentationmeasurement.blocked_countmeasurement.manual_countrelationship_health.gapscheckpoint.pendingcheckpoint.pending.blockersruntime.codex_cliruntime.claude_codestateblockedmanualevidencefacts.expected_eventsfacts.instrumentationfacts.provider_statefacts.app_stackfacts.deployfacts.commercefacts.emailfacts.measurementrecommended_actionsourcechild_descriptor
Shared source gates: updates_repairs_migrations, file_writes,
checkpoint, provider_mutation, publishing_or_spend, customer_contact,
private_data, destructive_operations, structured_collection,
public_issue_or_proposal, account_change, upload_assets,
budget_change, campaign_publish, conversion_upload, gtm_publish.
What ships with it
29 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.
- references/compliance/angle-playbook.md 12 KB
- references/compliance/ftc-scrutiny-categories.md 6.0 KB
- references/compliance/README.md 3.2 KB
- references/compliance/testimonial-decision-rubric.md 2.9 KB
- references/entry-points.md 8.7 KB
- references/google-ads-campaign-plan.md 24 KB
- references/image-generation-workflow.md 42 KB
- references/image-prompt-templates.md 7.9 KB
- references/launch-plan-check.md 5.5 KB
- references/lenses/copy-quality.md 4.9 KB
- references/lenses/ftc-compliance.md 3.2 KB
- references/lenses/meta-policy.md 6.4 KB
- references/lenses/README.md 1.9 KB
- references/lenses/substantiation.md 4.8 KB
- references/lenses/visual-standards.md 4.4 KB
- references/lenses/voice-authenticity.md 3.7 KB
- references/long-form-video-ads.md 1.4 KB
- references/meta-ads-integration.md 9.4 KB
- references/mode-hook-library.md 4.0 KB
- references/mode-review.md 2.4 KB
- references/mode-static-ads.md 3.2 KB
- references/mode-video-scripts.md 1.5 KB
- references/one-liner-examples.md 4.6 KB
- references/one-liner-methodology.md 21 KB
- references/post-generation-pipeline.md 8.7 KB
- references/preflight-algorithm.md 8.8 KB
- references/review-workflow.md 5.1 KB
- references/static-output-template.md 8.2 KB
- references/video-templates-hooks.md 1.9 KB
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 · 500 lines · 136 tokens per session scan A e0ab0db6eee5
mb-ads is a skill published in the GitHub repository noontide-co/mainbranch (37 stars, last pushed 17d ago), licensed MIT. It adds 136 tokens to every session and 5,897 once invoked, about $0.0007 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
review-pr
Review a Dograh pull request, branch diff, or pasted patch for repo-specific security and correctness risks that are not obvious from generic FastAPI, Next.js, or Python conventions. Use when the user asks to review a PR, audit a diff, check whether changes are safe to merge, review their own changes, or asks what to…
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
cli-commands
MUST use when using the CLI, including debugging job failures and inspecting run history via wmill job.
native-trigger
Guidance for adding native trigger services to Windmill. Use when implementing or modifying native trigger integrations across the backend and frontend.
write-script-python3
MUST use when writing Python scripts.
write-workflow-as-code
MUST use when writing or modifying Windmill Workflow-as-Code scripts using workflow, task, step, sleep, approvals, taskScript, taskFlow, taskscript, or taskflow.