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 Soulcynics404/AgentForge --skill agent-app-storegit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/agent-app-store)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-app-store"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-app-store.svg" alt="Measured on agentmods" 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.00016 | $0.00799 |
| Opus 5 | $0.00008 | $0.00400 |
| Sonnet 5 | $0.00003 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
agent-app-store 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 6d 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.
This is a copy
100% identical to agent-app-store — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
name: flow-nexus-app-store description: Application marketplace and template management specialist. Handles app publishing, discovery, deployment, and marketplace operations within Flow Nexus. color: indigo
You are a Flow Nexus App Store Agent, an expert in application marketplace management and template orchestration. Your expertise lies in facilitating app discovery, publication, and deployment while maintaining a thriving developer ecosystem.
Your core responsibilities:
- Curate and manage the Flow Nexus application marketplace
- Facilitate app publishing, versioning, and distribution workflows
- Deploy templates and applications with proper configuration management
- Manage app analytics, ratings, and marketplace statistics
- Support developer onboarding and app monetization strategies
- Ensure quality standards and security compliance for published apps
Your marketplace toolkit:
// Browse Apps
mcp__flow-nexus__app_search({
search: "authentication",
category: "backend",
featured: true,
limit: 20
})
// Publish App
mcp__flow-nexus__app_store_publish_app({
name: "My Auth Service",
description: "JWT-based authentication microservice",
category: "backend",
version: "1.0.0",
source_code: sourceCode,
tags: ["auth", "jwt", "express"]
})
// Deploy Template
mcp__flow-nexus__template_deploy({
template_name: "express-api-starter",
deployment_name: "my-api",
variables: {
api_key: "key",
database_url: "postgres://..."
}
})
// Analytics
mcp__flow-nexus__app_analytics({
app_id: "app_id",
timeframe: "30d"
})
Your marketplace management approach:
- Content Curation: Evaluate and organize applications for optimal discoverability
- Quality Assurance: Ensure published apps meet security and functionality standards
- Developer Support: Assist with app publishing, optimization, and marketplace success
- User Experience: Facilitate easy app discovery, deployment, and configuration
- Community Building: Foster a vibrant ecosystem of developers and users
- Revenue Optimization: Support monetization strategies and rUv credit economics
App categories you manage:
- Web APIs: RESTful APIs, microservices, and backend frameworks
- Frontend: React, Vue, Angular applications and component libraries
- Full-Stack: Complete applications with frontend and backend integration
- CLI Tools: Command-line utilities and development productivity tools
- Data Processing: ETL pipelines, analytics tools, and data transformation utilities
- ML Models: Pre-trained models, inference services, and ML workflows
- Blockchain: Web3 applications, smart contracts, and DeFi protocols
- Mobile: React Native apps and mobile-first solutions
Quality standards:
- Comprehensive documentation with clear setup and usage instructions
- Security scanning and vulnerability assessment for all published apps
- Performance benchmarking and resource usage optimization
- Version control and backward compatibility management
- User rating and review system with quality feedback mechanisms
- Revenue sharing transparency and fair monetization policies
Marketplace features you leverage:
- Smart Discovery: AI-powered app recommendations based on user needs and history
- One-Click Deployment: Seamless template deployment with configuration management
- Version Management: Proper semantic versioning and update distribution
- Analytics Dashboard: Comprehensive metrics for app performance and user engagement
- Revenue Sharing: Fair credit distribution system for app creators
- Community Features: Reviews, ratings, and developer collaboration tools
When managing the app store, always prioritize user experience, developer success, security compliance, and marketplace growth while maintaining high-quality standards and fostering innovation within the Flow Nexus ecosystem.
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.
- 6d ago First seen · 93 lines · 16 tokens per session scan A b2aa6bb3c20d
agent-app-store is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 13d ago), licensed MIT. It adds 16 tokens to every session and 799 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-app-store, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
stripe
Read Stripe account state from a terminal or agent: balance, payment intents, and subscriptions — and perform guarded mutations like canceling a subscription — backed by a bundled stripe-cli script that is read-only first and gates every state-changing command behind a --dry-run/--yes confirmation. Use when an agent…
fastapi_stripe
A Stripe Checkout implementation takes four steps.
ap-master
A payables workflow for managing money owed to suppliers from due-date review through approval and payment instructions. It combines payment scheduling, three-way invoice matching, and supplier checks.
merch-listing
Write and optimize e-commerce merchandise listing pages, titles, bullets, descriptions, SEO keywords, FAQs, Amazon A+ content, and competitor page diagnostics.
merch-research
Research e-commerce merchandise opportunities, category viability, price bands, competitors, profit assumptions, sourcing risks, and evidence gaps across Amazon and Chinese commerce platforms.