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 akiotanaka847/qaio-desktop --skill schedule-my-revenuegit clone --depth 1 https://github.com/akiotanaka847/qaio-desktopWrote 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/akiotanaka847/qaio-desktop/schedule-my-revenue)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/schedule-my-revenue"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/schedule-my-revenue/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/akiotanaka847/qaio-desktop/schedule-my-revenue"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/schedule-my-revenue.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.00102 | $0.02141 |
| Opus 5 | $0.00051 | $0.01071 |
| Sonnet 5 | $0.00020 | $0.00428 |
| Haiku 4.5 | $0.00010 | $0.00214 |
Grade A, and why
schedule-my-revenue 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 12d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule My Revenue
Turn a signed contract into a month-by-month ASC 606 recognition schedule. One JSON artifact per contract, grouped by customer. Common patterns are baked in; the genuinely judgment-heavy stuff (variable consideration, significant financing, non-cash) gets flagged so you can decide. I summarize options, I never decide, and I never post.
When to use
- "build the revenue recognition schedule for {customer}" / "spread this contract".
- "build the ASC 606 schedule" / "ASC 606 recognition for this contract" - same flow, founder-side phrasing.
- "the customer renewed / upgraded / added a SKU - update revenue recognition".
- "we invoiced this annually; recognize it monthly".
- Called by
close-my-monthas part of revenue recognition pass, once per active contract.
Connections I need
I run external work through Composio. Before this skill runs I check that the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.
- Stripe (billing) — preferred source for subscription contracts, line items, and billing cadence. Required if Stripe is your contract source.
- HubSpot (CRM) — alternate / supplement source for signed contracts and SKU-level pricing. Optional.
If neither is connected I fall back to a dropped contract file (PDF, DOCX, CSV) or pasted summary. If you have nothing to share I stop and ask you to connect Stripe or drop the contract.
Information I need
I read your bookkeeping context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.
- The contract itself — Required. Why: I can't build a recognition schedule without effective date, end date, line items, and pricing. If missing I ask: "Can you share the signed contract? Connecting Stripe or HubSpot is easiest, otherwise drop the PDF or paste the line items."
- Your revenue model and ASC 606 posture — Required. Why: subscription vs. usage vs. services changes how each performance obligation is recognized. If missing I ask: "How does the business make money, subscriptions, usage-based, services, or a mix? And are you trying to follow ASC 606 strictly or staying on cash?"
- A chart of accounts with deferred revenue and revenue lines — Required. Why: I draft the journal entry stubs against real account codes, never invented ones. If missing I ask: "Do we have a chart of accounts yet with a deferred revenue line? If not, let's draft one first."
- Whether this is a new contract or a modification — Optional. Why: changes whether I treat it as a fresh schedule or a prospective / cumulative-catch-up modification. If missing I ask: "Is this a brand-new customer contract or an upsell or change to an existing one? If you don't have it I assume new and flag it for you to confirm."
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.
- 12d ago First seen · 120 lines · 102 tokens per session scan A 4bf8b2214c9f
schedule-my-revenue is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 102 tokens to every session and 2,141 once invoked, about $0.0005 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-31.
Other skills, from other repositories
assess
A Japanese tax-filing assessment guide that asks about your income, family, and business situation to identify which tax returns you may need.
setup
A setup wizard for shinkoku, a Japanese tax-filing tool. It creates or updates the configuration file and initializes the tool’s database.
furusato
A Japanese hometown-tax donation manager for furusato nozei, a system where donations to municipalities can qualify for an income-tax or local-tax deduction. It reads donation receipts, stores donation records, and calculates deduction limits.
tax-advisor
A Japanese tax-advice skill based on 2025 tax rules. It answers tax-filing and tax-saving questions using documents in a reference folder rather than general guesses.
e-bookkeeping-compliance
A compliance checker for Japan's rules on keeping high-quality electronic accounting books. It checks whether accounting records and related documentation meet specified requirements for electronic storage.
incorporation
A guide for moving from working as an individual business owner to operating through a company in Japan. It covers company types, setup steps, officer pay, taxes, and social insurance.