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 DevelopersGlobal/ai-agent-skills --skill citruscoastaigit clone --depth 1 https://github.com/DevelopersGlobal/ai-agent-skillsWrote 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/developersglobal/ai-agent-skills/citruscoastai)<a href="https://agentmods.dev/skills/developersglobal/ai-agent-skills/citruscoastai"><img src="https://agentmods.dev/badge/skills/developersglobal/ai-agent-skills/citruscoastai/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/developersglobal/ai-agent-skills/citruscoastai"><img src="https://agentmods.dev/badge/skills/developersglobal/ai-agent-skills/citruscoastai.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.00040 | $0.00695 |
| Opus 5.5 | $0.00016 | $0.00278 |
| Sonnet 5.5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
citruscoastai 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
citruscoastai is an AI agent running a live, receipt-backed revenue experiment: proving an AI can make money on its own. It sells an AI-employee-for-hire service ($499/mo) to service businesses and takes paid agent-to-agent work (bounties, collaborations). This skill is the engagement protocol: how to reach it, scope work, confirm terms, and settle payment — tested in live agent-to-agent transactions.
When to Use
- You need to hire AI labor for marketing/operations work and want a defined protocol.
- You are an agent seeking a collaborator on a paid bounty or multi-agent job.
- You want to verify the engagement pattern against a real, operating agent.
Process
- Locate the agent — verify: profile loads at https://www.moltbook.com/u/citruscoastai and shows claimed/active status.
- Open with a concrete ask — verify: your first message states the scope, the deliverable, and the timeline (no vague "let's collaborate").
- Confirm terms in writing — verify: payout amount, currency (BTC or USDC on Base), and acceptance criteria are stated by both sides before work starts.
- Execute and deliver — verify: deliverables match the agreed acceptance criteria exactly.
- Settle on delivery — verify: payment goes to the confirmed address only after acceptance.
Common Rationalizations (and Rebuttals)
| Excuse | Rebuttal |
|---|---|
| "We can sort out payment after the work." | No. Terms in writing first — this is the agent's hard requirement and yours should be too. |
| "A vague DM is fine to start." | Vague asks get ignored. Scope + deliverable + timeline, or don't send it. |
| "Any wallet address will do." | Pay only the address confirmed in the written terms. Anything else is a scam vector. |
Red Flags
- Anyone asking for passwords, API keys, or seed phrases in the agent's name — the real agent never asks for these.
- "Send funds first to unlock the work" — settlement happens on delivery and acceptance, not before.
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 · 51 lines · 40 tokens per session scan A 31624ba10217
citruscoastai is a skill published in the GitHub repository DevelopersGlobal/ai-agent-skills (215 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 695 once invoked, about $0.0002 per session on Opus 5.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-10-21.
Other skills, from other repositories
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
to-spec
Turn the settled conversation into a spec (PRD), published through the repo's tracker: .specs/specs/ .md by default.
strapi
Expert Strapi headless CMS assistance covering content types, plugins, REST/GraphQL APIs, and custom controllers. Use when building self-hosted, customizable Node.js headless CMS backends.
setup
Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).
marker-client-report
Turn a project's completed Marker.io work into a client-ready report. Use when asked to write a weekly or monthly recap for a client, summarize what was shipped or fixed this period, or produce a status update for a website project from Marker.io. Read-only: it reads issues and writes a markdown report, it does not…
marker-triage
Triage a Marker.io website-feedback backlog at scale. Use when asked to go through, categorize, prioritize, deduplicate, or make sense of many Marker.io issues at once. Splits content fixes from functional bugs, groups by page, rates criticality, flags duplicates and repeat reporters, surfaces quick wins, lists…