agentic-income
Skill5 starsChanged 45 days agoMITView on GitHub
Build and operate principal-owned AI income systems that perform accepted paid work. Use when discovering an agent service opportunity, validating demand, creating an Outcome Pack, implementing a vertical AI system, defining agent authority, evaluating delivery, exposing a Skill/MCP/A2A service, or proving net economics. Active services belong here; affiliate and owned income assets belong to Agentic Passive Income; capital, crypto, lending, staking, trading, and yield experiments belong to DPI.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Starlight-Intelligence/starlight-agent-skillstheir own version, first seen Nov 8, 2026
- frankxai/starlight-agent-skillstheir own version, first seen Jul 27, 2026
- frankxai/affiliate-agent-skillstheir own version, first seen Jul 3, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- frankxai/affiliate-agent-skills★ 2same name
- frankxai/starlight-agent-skills★ 1same name
- Starlight-Intelligence/starlight-agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- affiliate-auditSkill
- quote-deskSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
If MODE is omitted, infer it from the request and state the inferred mode.
- Distinctive: line 34
Every build must produce or update:
- Distinctive: line 99
Verify routine, authority, security, recovery, cost, and latency evals.
- Distinctive: line 106
Never use invoice screenshots as proof.
- Distinctive: line 121
Use examples/request-to-quote-desk as the beachhead.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agentic Income
Agentic Income turns a repeated professional workflow into a governed, sellable service.
The agent is an operator. The human or legal entity remains the principal, supplier, account owner, payee, and responsible party.
Invocation
Use:
/agentic-income MODE GOALModes:
- discover — rank opportunities by buyer pain, access, evidence, risk, time to cash, repeatability, and support burden.
- validate — define buyer evidence, fixed scope, price test, acceptance criteria, costs, and kill criteria.
- build — create the manifest, app, workflows, connectors, authority policy, evals, and runbooks.
- sell — create a demo, landing page, proposal, and reviewed outreach assets.
- deliver — deploy into customer-owned accounts and run acceptance tests.
- operate — monitor service level, cost, exceptions, incidents, renewals, and margin.
- publish — expose a safe Skill, MCP tool, A2A Agent Card, or metered endpoint.
- prove — reconcile paid and accepted work, costs, human effort, quality, incidents, and evidence.
- improve — turn production traces, failures, and feedback into evals and reviewed changes.
If MODE is omitted, infer it from the request and state the inferred mode.
Outcome Pack contract
Every build must produce or update:
- income-system.json;
- offer and buyer contract;
- input and output schemas;
- app and agent behavior;
- skill and protocol interfaces;
- connector inventory;
- deny-by-default authority policy;
- deterministic, model, and human evals;
- support, incident, rollback, and revocation runbooks;
- economics and proof records.
Validate against schemas/income-system.v1.schema.json.
Opportunity ranking
Prefer:
- A painful workflow with existing budget and a short path to acceptance.
- A narrow buyer and repeatable input/output contract.
- Customer-owned systems and credentials.
- Fixed scope and transparent pricing.
- Deterministic acceptance, low support, and reusable implementation.
- Recurring assurance earned through monitoring, evals, and updates.
Reject:
- vague “AI transformation” without a buyer or accepted outcome;
- regulated decisions in medical, employment, credit, insurance, or legal advice;
- unrestricted wallet, bank, email, or production authority;
- arbitrary bespoke integrations;
- autonomous cold outreach;
- revenue guarantees, custody, pooled payouts, or performance fees without clean attribution;
- generic agent marketplace before verified supply and demand exist.
Authority model
Bind every service to:
Legal principal → agent identity → capability → scoped credential → policy → auditable action.
Agents may research, classify, draft, schedule, update approved records, run tests, and propose reversible changes.
Human approval is mandatory for:
- prices and binding quotes;
- contracts and legal terms;
- person-directed broadcasts;
- refunds outside policy;
- production credentials or wider permissions;
- bank or wallet transfers;
- budget increases;
- destructive or irreversible actions;
- public income claims.
An operational email is not legal identity. A delegated wallet signer is not wallet ownership. Wallet keys, bank credentials, and seed phrases never enter model context.
Build loop
- Observe the buyer workflow and collect payment evidence.
- Score opportunity, risk, repeatability, and support.
- Propose one Outcome Pack.
- Validate offer, acceptance, budget, authority, and stop conditions.
- Build in a branch or sandbox.
- Verify routine, authority, security, recovery, cost, and latency evals.
- Deploy into customer-owned accounts.
- Reconcile accepted outcomes, money, costs, incidents, and owner time.
- Improve or retire from evidence.
Proof contract
Never use invoice screenshots as proof.
Record:
- quoted, authorized, invoiced, paid, earned, refunded, and adjusted events;
- customer acceptance;
- system and eval versions;
- direct platform, model, tool, support, and owner-time costs;
- completion, exception, and incident rates;
- evidence level: reported, document-reviewed, connector-observed, or independently attested.
Public claims require consent and human approval.
First reference system
Use examples/request-to-quote-desk as the beachhead.
It is for renovation, commercial maintenance, specialist installation, and B2B technical services. It qualifies inbound requests, asks for missing information, schedules estimates, drafts non-binding quotes, updates the CRM, and routes commercial commitments to a human.
The recommended validation model is a fixed deployment plus recurring managed assurance. Do not charge a performance fee initially.
Protocol posture
- Agent Skills carry operating knowledge.
- MCP connects tools and data.
- A2A exposes remote task services and signed Agent Cards.
- AP2 can represent payment authority.
- UCP and ACP can support commerce discovery and checkout.
- x402 can meter capped machine endpoints.
Compose these protocols. Do not fork them or create a new agent framework.
The innovation is the service and proof contract binding principal, outcome, authority, system version, evaluation, economics, and evidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

