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 AtlasOmnia/donna-starter --skill meta-business-postinggit clone --depth 1 https://github.com/AtlasOmnia/donna-starterWrote 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/atlasomnia/donna-starter/meta-business-posting)<a href="https://agentmods.dev/skills/atlasomnia/donna-starter/meta-business-posting"><img src="https://agentmods.dev/badge/skills/atlasomnia/donna-starter/meta-business-posting/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/skills/atlasomnia/donna-starter/meta-business-posting"><img src="https://agentmods.dev/badge/skills/atlasomnia/donna-starter/meta-business-posting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 46 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 22 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Data Exfiltration · line 60 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00042 | $0.01115 |
| Opus 5 | $0.00021 | $0.00558 |
| Sonnet 5 | $0.00008 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
meta-business-posting scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://graph.facebook.com/v21.0/$META_PAGE_ID/feed" \ Copies of this mod
1 near-identical copy found in the catalogue:
- meta-business-posting — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta / Facebook Page Posting
Publish posts to a Facebook Page using the user's own account. Two paths: the browser session (primary — works for everyone) and the Graph API (power users with a Meta app).
Hard rules
- Never ask the user to paste a Facebook password, 2FA code, or token into chat. The user logs in through the browser themselves; tokens live in
.env. - Posting is an irreversible publish action. Draft the full post (text, link, image), show the user exactly what will be published and to which Page, and get explicit approval before submitting.
- Post as the Page, not as the user's personal profile, unless the user explicitly says otherwise.
- Never delete or edit a published post without explicit approval.
- Respect platform policies: no engagement bait, spam, or misleading claims; no posting to Pages the user does not administer.
- If a login, 2FA, or app-review wall appears, stop and hand it to the user — never work around security checkpoints.
Path 1 — Browser session (recommended)
Facebook's business surfaces are heavily JS-gated; the Hermes browser tools handle them naturally.
- User logs in once: navigate to
facebook.com(orbusiness.facebook.com) in the Hermes browser and have the user complete login and any 2FA themselves. The agent never sees credentials. - Locate the composer: navigate to the Page (e.g.
facebook.com/<page>→Create post, or Meta Business Suite → Content → Create post). - Draft: compose text, optionally attach an image via the page's file input (Hermes browser
set_input_files/ upload control). Do not publish yet. - Confirm identity: check the "Posting as" selector shows the intended Page, not the personal profile.
- Get approval: show the user the drafted post and the target Page; publish only on explicit approval.
- Publish and verify: click Publish (or have the user click it), then verify the post appears in the Page's feed and capture its permalink for the user.
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 · 95 lines · 42 tokens per session scan A 8ae341911770
meta-business-posting is a skill published in the GitHub repository AtlasOmnia/donna-starter (111 stars, last pushed 13d ago), licensed MIT. It adds 42 tokens to every session and 1,115 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
npm-downloads-to-leads
Takes a list of npm package names (yours or competitors'), fetches 12 weeks of daily download data from the npm API, computes a breakout velocity score per package to identify hockey-stick growth, fetches maintainer profiles from the npm registry and GitHub API, and outputs a ranked lead brief for each breakout…
gh-issue-to-demand-signal
Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's…
domain-expired-opportunity-finder
Evaluates expired domain candidates against a target niche, scores them by topical relevance, historical activity level, and history cleanliness, then outputs a ranked shortlist with explainable reasoning and risk flags.
company-radar
Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.
linkedin-job-post-to-buyer-pain-map
Takes pasted LinkedIn job posts or hiring descriptions and converts them into a structured buyer pain map with inferred pains, capability gaps, buy-vs-build signal, account priority scores, and suggested outreach angles. Use when asked to analyze hiring posts, decode job descriptions for buyer intent, build a pain map…
producthunt-launch-kit
Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Generates tagline variants under 60 chars, a 500-char description, a maker comment, launch-day tweet thread, LinkedIn post, and a 4-email launch sequence.