QuickBooks Online Integration
hewi333/Mom-n-Pop-Skills
Connects a small business to QuickBooks Online for customers, estimates, invoices and payments, using Intuit OAuth 2.0 with token refresh and sandbox or production setups.
Creates, updates, and monitors Privacy.com virtual payment cards with spending limits for an agent making controlled purchases.
Install Privacy.com Virtual Cards
$ npx skills add dylanfeltus/skills --skill privacy-cards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dylanfeltus/skills privacy-cards --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dylanfeltus/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/privacy-cards .claude/skills/privacy-cards && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "privacy-cards" agent skill from https://github.com/dylanfeltus/skills/tree/main/privacy-cards into .claude/skills/privacy-cards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-cards", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dylanfeltus/skills/tree/main/privacy-cardsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dylanfeltus/skills --skill privacy-cards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dylanfeltus/skills privacy-cards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dylanfeltus/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/privacy-cards .agents/skills/privacy-cards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "privacy-cards" agent skill from https://github.com/dylanfeltus/skills/tree/main/privacy-cards into .agents/skills/privacy-cards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-cards", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dylanfeltus/skills --skill privacy-cards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dylanfeltus/skills privacy-cards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dylanfeltus/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/privacy-cards .cursor/skills/privacy-cards && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "privacy-cards" agent skill from https://github.com/dylanfeltus/skills/tree/main/privacy-cards into .cursor/skills/privacy-cards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-cards", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dylanfeltus/skills.git --path privacy-cards--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dylanfeltus/skills --skill privacy-cards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dylanfeltus/skills privacy-cards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dylanfeltus/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/privacy-cards .gemini/skills/privacy-cards && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "privacy-cards" agent skill from https://github.com/dylanfeltus/skills/tree/main/privacy-cards into .gemini/skills/privacy-cards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-cards", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dylanfeltus/skills privacy-cardsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dylanfeltus/skills --skill privacy-cards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dylanfeltus/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/privacy-cards .github/skills/privacy-cards && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "privacy-cards" agent skill from https://github.com/dylanfeltus/skills/tree/main/privacy-cards into .github/skills/privacy-cards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-cards", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dylanfeltus/skills --skill privacy-cards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dylanfeltus/skills privacy-cards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dylanfeltus/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/privacy-cards .opencode/skills/privacy-cards && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "privacy-cards" agent skill from https://github.com/dylanfeltus/skills/tree/main/privacy-cards into .opencode/skills/privacy-cards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "privacy-cards", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
privacy-cards- GitHub stars
- 179
- Token cost
- ~2.2k tokens
- SKILL.md length
- 749 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Creates, updates, and monitors Privacy.com virtual payment cards with spending limits for an agent making controlled purchases.
- Works in 6 steps: Determine the amount needed (round up to… → Choose card type → Create the card and extract only the… → …
- Setting up a spend-limited card for one specific purchase
- SKILL.md covers When to Use, Setup, API Reference and Step-by-Step Instructions, plus 5 more sections
- Calls curl and python3; reaches api.privacy.com and sandbox.privacy.com; needs PRIVACY_API_KEY and CARD_TOKEN
What it does
A single Privacy.com API, reached with an API key, backs the whole skill: creating a single-use, merchant-locked, or digital-wallet card with an optional spend limit and duration, updating a card's state or limit afterward, and listing cards or their recent transactions. A sandbox base URL is available for testing separately from the production API, and closing a card is explicitly permanent.
When your agent uses it
- Setting up a spend-limited card for one specific purchase
- Checking a card's status or recent transactions
- Pausing or permanently closing a virtual card
Example prompts
- “Create a single-use card with a $25 limit for this domain purchase.”
- “Check the transaction history on the card I made yesterday.”
- “Pause the card tagged for the trial subscription.”
Requirements
- A Privacy.com account and API key (`PRIVACY_API_KEY`)
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Determine the amount needed (round up to whole dollars)
- Choose card type
- Create the card and extract only the fields you need. Never log or print the full API response — it contains the full card number (PAN)…
- When you need the full card details for checkout, extract them in a separate step that is not logged to chat. Use the card details…
- Use these card details to complete the purchase (via browser tool or API)
- After purchase, verify with the transactions endpoint
What it can do on your machine
Read from SKILL.md and the folder at commit b97a48f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curlpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
api.privacy.comsandbox.privacy.com
Also links to:
privacy-com.readme.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
PRIVACY_API_KEYCARD_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Privacy.com Virtual Cards loads about 2.2k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 749 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dylanfeltus/skills at commit b97a48f, republished under its MIT licence (© dylanfeltus). 749 words, ~2,213 tokens.
Download SKILL.mdSave it as
.claude/skills/privacy-cards/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- privacy-cards
- description
- Create and manage Privacy.com virtual cards for agent spending. Use when an agent needs to make a purchase, buy a domain, pay for a service, or needs a disposable card with a spending limit. Requires a Privacy.com account and API key.
Privacy.com Virtual Cards
Create, manage, and monitor virtual cards via the Privacy.com API. Designed for AI agents that need to make purchases with controlled spending limits.
When to Use
- Agent needs to buy something (domain, API access, subscription, physical goods)
- Agent needs a disposable card for a one-time purchase
- User wants to create a spend-limited card for a specific merchant
- User asks to check card status or recent transactions
- User wants to pause or close a card
Setup
Requires the PRIVACY_API_KEY environment variable. Get an API key from your Privacy.com account settings.
Plans and card limits:
- Free: 12 cards/month
- Pro ($10/mo): 36 cards/month
- Premium ($25/mo): 60 cards/month
Sandbox: Use https://sandbox.privacy.com/v1 for testing. Production: https://api.privacy.com/v1.
API Reference
Base URL: https://api.privacy.com/v1
Auth Header: Authorization: api-key YOUR_API_KEY
Content-Type: application/json
All monetary amounts are in cents (e.g., $25.00 = 2500).
Create a Card
POST https://api.privacy.com/v1/cards
{
"type": "SINGLE_USE",
"memo": "Domain purchase - example.com",
"spend_limit": 2500,
"spend_limit_duration": "TRANSACTION",
"state": "OPEN"
}Parameters:
| Field | Required | Description |
|---|---|---|
type | Yes | SINGLE_USE (auto-closes after one charge), MERCHANT_LOCKED (locks to first merchant), DIGITAL_WALLET (Apple/Google Pay) |
memo | No | Label for the card (what it's for) |
spend_limit | No | Max spend in cents. Must be whole dollars (e.g., 2500 not 2550) |
spend_limit_duration | No | TRANSACTION (per charge), MONTHLY, ANNUALLY, FOREVER |
state | No | OPEN (ready to use) or PAUSED |
exp_month | No | Two-digit expiry month (auto-generated if omitted) |
exp_year | No | Four-digit expiry year (auto-generated if omitted) |
Response includes: pan (16-digit card number), cvv, exp_month, exp_year, token (card ID), last_four.
Update a Card
PATCH https://api.privacy.com/v1/cards/{card_token}
{
"state": "PAUSED",
"spend_limit": 5000,
"memo": "Updated memo"
}Can update: state, memo, spend_limit, spend_limit_duration, funding_token.
Setting state to CLOSED is permanent and cannot be undone.
Get Card(s)
GET https://api.privacy.com/v1/cards/{card_token}
GET https://api.privacy.com/v1/cards
GET https://api.privacy.com/v1/cards?begin=2024-01-01&end=2024-12-31&page=1&page_size=50Query parameters: begin, end (date filters), page, page_size (pagination).
List Transactions
GET https://api.privacy.com/v1/transactions?card_token={token}&result=APPROVED&page=1&page_size=50Query parameters:
| Field | Description |
|---|---|
card_token | Filter by card |
result | APPROVED or decline reason |
page | Page number (1-indexed) |
page_size | Results per page |
begin | Start date (YYYY-MM-DD) |
end | End date (YYYY-MM-DD) |
Transaction statuses: PENDING, SETTLING, SETTLED, VOIDED, BOUNCED, DECLINED
Step-by-Step Instructions
Creating a Card for an Agent Purchase
- Determine the amount needed (round up to whole dollars)
- Choose card type:
- One-time purchase? Use
SINGLE_USE - Recurring at one merchant (e.g., subscription)? Use
MERCHANT_LOCKED
- One-time purchase? Use
- Create the card and extract only the fields you need. Never log or print the full API response — it contains the full card number (PAN) and CVV which must not appear in chat logs or transcripts.
# Create card and extract only safe fields for logging
RESPONSE=$(curl -s https://api.privacy.com/v1/cards \
-X POST \
-H "Authorization: api-key $PRIVACY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "SINGLE_USE",
"memo": "Purpose of purchase",
"spend_limit": AMOUNT_IN_CENTS,
"spend_limit_duration": "TRANSACTION",
"state": "OPEN"
}')
# Log only safe fields (no PAN/CVV)
echo "$RESPONSE" | python3 -c "
import sys, json
card = json.load(sys.stdin)
print(json.dumps({
'token': card.get('token'),
'last_four': card.get('last_four'),
'exp_month': card.get('exp_month'),
'exp_year': card.get('exp_year'),
'spend_limit': card.get('spend_limit'),
'state': card.get('state'),
'memo': card.get('memo')
}, indent=2))
"- When you need the full card details for checkout, extract them in a separate step that is not logged to chat. Use the card details directly in the browser tool or API call without printing them.
# Extract card details for checkout (DO NOT print to chat)
PAN=$(echo "$RESPONSE" | python3 -c "import sys,json; print(json.load(sys.stdin)['pan'])")
CVV=$(echo "$RESPONSE" | python3 -c "import sys,json; print(json.load(sys.stdin)['cvv'])")
EXP_MONTH=$(echo "$RESPONSE" | python3 -c "import sys,json; print(json.load(sys.stdin)['exp_month'])")
EXP_YEAR=$(echo "$RESPONSE" | python3 -c "import sys,json; print(json.load(sys.stdin)['exp_year'])")- Use these card details to complete the purchase (via browser tool or API)
- After purchase, verify with the transactions endpoint
Checking a Card's Status
curl -s https://api.privacy.com/v1/cards/CARD_TOKEN \
-H "Authorization: api-key $PRIVACY_API_KEY"Pausing a Card (Temporarily Disable)
curl -s https://api.privacy.com/v1/cards/CARD_TOKEN \
-X PATCH \
-H "Authorization: api-key $PRIVACY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"state": "PAUSED"}'Closing a Card (Permanent)
curl -s https://api.privacy.com/v1/cards/CARD_TOKEN \
-X PATCH \
-H "Authorization: api-key $PRIVACY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"state": "CLOSED"}'Viewing Recent Transactions
curl -s "https://api.privacy.com/v1/transactions?page=1&page_size=10" \
-H "Authorization: api-key $PRIVACY_API_KEY"Show full SKILL.md (307 more words)Show less
Safety Rules
- Always confirm the purchase amount and purpose with the user before creating a card, unless the user has pre-approved the spend (e.g., "buy this domain" with a known price).
- Use
SINGLE_USEby default. Only useMERCHANT_LOCKEDif explicitly needed for recurring charges. - Set the spend limit as close to the expected amount as possible. Round up to the next whole dollar, but don't over-allocate (e.g., $12.99 item = $13.00 = 1300 cents).
- Close or pause cards after use.
SINGLE_USEcards auto-close, butMERCHANT_LOCKEDcards stay open. Close them when no longer needed. - Never log, print, or display the full PAN or CVV in chat, logs, or tool output. The raw API response contains sensitive card data (PAN, CVV) that must not appear in transcripts. Always parse the response and extract only safe fields (token, last_four, memo, spend_limit, state) for logging. Use full card details only in the checkout step, never echoed to chat.
- Include a descriptive memo on every card so the user can identify what it was for in their Privacy.com dashboard.
Output Format
When creating a card, report to the user:
Created Privacy.com card (****1234)
Type: Single-use
Limit: $25.00
Memo: Domain purchase - example.com
Status: Ready to useWhen listing transactions:
Recent transactions:
1. $12.99 at NAMECHEAP.COM - SETTLED (Jan 15, 2024)
Card: ****1234 (Domain purchase)
2. $49.00 at GITHUB.COM - PENDING (Jan 14, 2024)
Card: ****5678 (GitHub Pro subscription)Error Handling
- 401 Unauthorized: API key is invalid or missing. Check
PRIVACY_API_KEYenv var. - 403 Forbidden: Account may need verification or doesn't have API access.
- 429 Rate Limited: Back off and retry after a short delay.
- Card creation fails: May have hit the monthly card limit for the plan tier. Inform the user.
- Amount not in whole dollars: The API requires spend_limit in whole-dollar increments (in cents). Round up.
Sandbox Testing
For testing without real money, use the sandbox environment:
- Base URL:
https://sandbox.privacy.com/v1 - Simulate transactions:
POST https://sandbox.privacy.com/v1/simulate/authorizeandPOST https://sandbox.privacy.com/v1/simulate/clearing - Sandbox cards work identically to production but no real charges occur.
Data Source
Privacy.com Developer API - RESTful API, requires API key from a Privacy.com account.
© dylanfeltus, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in privacy-cards of dylanfeltus/skills.
- SKILL.md
- README.md
Open the folder on GitHubat commit b97a48f
Compare with similar skills
Privacy.com Virtual Cards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Privacy.com Virtual Cards this skilldylanfeltus/skills | 179 | — | ~2.2k | Automated safety check: Pass | MIT | |
| QuickBooks Online Integrationhewi333/Mom-n-Pop-Skills | 122 | — | ~1.9k | Automated safety check: Pass | MIT | |
| PayRam Payment AnalyticsPayRam/payram-mcp | 158 | — | ~4.1k | Automated safety check: Pass | None | |
| Billing Automationwshobson/agents | 40k | 13 repos | ~473 | Automated safety check: Pass | MIT | |
| Stripe Best Practicesfossasia/eventyay | 1.7k | 1 repos | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Pinme Uniwebpayglitternetwork/pinme | 3.8k | — | ~7.3k | Automated safety check: Pass | MIT |
Similar skills
PayRam Payment Analytics
PayRam/payram-mcp
Queries a PayRam server's dashboard data through its REST APIs with a Bearer token: payment search, daily volume, unswept balances, sweep history and on-ramp metrics.
Billing Automation
wshobson/agents
Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.
Stripe Best Practices
fossasia/eventyay
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…
Pinme Uniwebpay
glitternetwork/pinme
A skill your agent uses when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout…
- Official
AWS Marketplace Metering
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
More from dylanfeltus/skills
All 10 skills in this repoApp Store Intelligence
dylanfeltus/skills
Looks up app details, ratings and reviews and searches the iOS and Mac App Stores through Apple's free iTunes APIs, with a web-search fallback for Google Play.
AI Image Creative Direction
dylanfeltus/skills
Gives prompt templates, a model-selection guide and anti-generic rules for AI-generated visuals: hero images, feature illustrations, OG cards, icons and backgrounds.
Design Token Generator
dylanfeltus/skills
Generates type scales, color palettes, spacing systems, WCAG contrast checks and dark mode palettes from formulas, as CSS custom properties, a Tailwind config or JSON tokens.
Hacker News Search
dylanfeltus/skills
Searches and monitors Hacker News stories, comments and users through the free Algolia HN Search API, with tag, points and date filters.
Motion Design Patterns for React
dylanfeltus/skills
Framer Motion (Motion) patterns for React: spring presets, staggers, layout animations, micro-interactions, scroll effects and page transitions, with performance rules.
Product Hunt Search and Monitoring
dylanfeltus/skills
Looks up Product Hunt launches, products and makers through its GraphQL API: daily top posts, topic browsing and per-post details, using a free developer token.
Related
Categories
Questions about Privacy.com Virtual Cards
What does Privacy.com Virtual Cards do?
Creates, updates, and monitors Privacy.com virtual payment cards with spending limits for an agent making controlled purchases. com API, reached with an API key, backs the whole skill: creating a single-use, merchant-locked, or digital-wallet card with an optional spend limit and duration, updating a card's state or limit afterward, and listing cards or their recent transactions. A sandbox base URL is available for testing separately from the production API, and closing a card is explicitly permanent.
When should I use Privacy.com Virtual Cards?
Privacy.com Virtual Cards fits situations like: setting up a spend-limited card for one specific purchase; checking a card's status or recent transactions; pausing or permanently closing a virtual card.
How do I install Privacy.com Virtual Cards in Claude Code?
Run `npx skills add dylanfeltus/skills --skill privacy-cards -a claude-code`. Or copy the skill folder (privacy-cards in dylanfeltus/skills) into .claude/skills/privacy-cards in your project. Claude Code loads it when a task matches its description.
How do I install Privacy.com Virtual Cards in Codex?
Run `npx skills add dylanfeltus/skills --skill privacy-cards -a codex`. Or copy the skill folder (privacy-cards in dylanfeltus/skills) into .agents/skills/privacy-cards in your project. Codex loads it when a task matches its description.
Can I use Privacy.com Virtual Cards in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dylanfeltus/skills --skill privacy-cards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/privacy-cards, .gemini/skills/privacy-cards, .github/skills/privacy-cards and .opencode/skills/privacy-cards in your project.
What does Privacy.com Virtual Cards need to run?
Going by SKILL.md and its folder, Privacy.com Virtual Cards needs the command-line tools its instructions call (curl and python3) and credentials named PRIVACY_API_KEY and CARD_TOKEN. Our summary lists: A Privacy.com account and API key (`PRIVACY_API_KEY`).
Does Privacy.com Virtual Cards access the network?
SKILL.md names 3 domains. In commands or code: api.privacy.com and sandbox.privacy.com; the agent is likely to contact these when it follows the instructions. As links in the text: privacy-com.readme.io. This is read from the text; nothing was executed.
Is Privacy.com Virtual Cards safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Privacy.com Virtual Cards use?
Privacy.com Virtual Cards is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Privacy.com Virtual Cards use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Privacy.com Virtual Cards?
Skills that share tags, products or a category with Privacy.com Virtual Cards: QuickBooks Online Integration (hewi333/Mom-n-Pop-Skills, 122 stars), PayRam Payment Analytics (PayRam/payram-mcp, 158 stars), Billing Automation (wshobson/agents, 40k stars) and Stripe Best Practices (fossasia/eventyay, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Privacy.com Virtual Cards?
dylanfeltus (a GitHub user) maintains it in dylanfeltus/skills, which has 179 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 17, 2026.
Source: dylanfeltus/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.