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/seenode/seenode-agent-plugin/billingnpx skills add seenode/seenode-agent-plugin --skill billinggit clone --depth 1 https://github.com/seenode/seenode-agent-pluginWhat 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.00070 | $0.00783 |
| Opus 5 | $0.00035 | $0.00392 |
| Sonnet 5 | $0.00014 | $0.00157 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
billing 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Billing and credits on Seenode
Present money to users from *Usd fields only (creditBalanceUsd, totalCostUsd, pricePerMonthUsd, totalAmountUsd, etc.). Treat *Cents as the exact ledger unit — do not present it as dollars. Never manually divide or quote ambiguous fields like totalCost, pricePerMonth, or amount as dollars.
Read-only overview (start here)
get_credit_balance() # prepaid balance (not MTD spend)
get_team_usage() # unbilled usage + month-end projection
get_spending(range="this_month") # this_month | last_month | last_7_days | custom
list_billing_orders(page=1)
list_credit_ledger(page=1, kind=null, period_from=null, period_to=null)
get_billing_information()
get_bonus_credit_rate()
For get_spending with range="custom", pass period_start and period_end (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS).
Use this skill before paid creates (create_database, paid packages, storage) when balance may be insufficient. Deployment LIMITS often pairs with get_team_limits (see projects) plus credit checks here.
Browser flows (preferred mutations)
Prefer sending the user a URL over handling Stripe secrets in chat:
get_billing_portal_url() # manage payment methods / address / tax
create_checkout_session(price=null) # top up prepaid credits; price in dollars, min 10 when set
Show checkoutSessionUrl / portal URL as a markdown link. Links may be short-lived.
Money mutations (confirm first)
Always summarize what will happen and get explicit approval:
pay_now() # settle current unbilled usage against prepaid credits
create_setup_intent() # returns clientSecret for Stripe.js — avoid unless portal/checkout cannot work
Before pay_now, show get_credit_balance + get_team_usage so the user knows the charge. Prefer get_billing_portal_url / create_checkout_session over create_setup_intent — do not paste or linger on clientSecret in chat; if returned, tell the user to complete setup in a proper Stripe UI rather than treating chat as a card form.
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 · 69 lines · 70 tokens per session scan A fb6c233d94ea
billing is a skill published in the GitHub repository seenode/seenode-agent-plugin (2 stars, last pushed 23d ago), licensed MIT. It adds 70 tokens to every session and 783 once invoked, about $0.0003 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
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
cabloy-worktree-environment
This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup. It prepares a confirmation-gated, worktree-local Vona and Zova runtime environment for a linked Cabloy Basic or Cabloy Start Git worktree using Git…
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…