Bankr Dev Project Templates
- 353 installs
- 80 repo stars
- Updated March 24, 2026
- bankrbot/claude-plugins
bankr dev - project templates is a Claude skill that scaffolds four Bankr Agent API project archetypes—bot, web-service, dashboard, and CLI—for developers who need vetted directory structures and starter patterns before
About
bankr dev - project templates is a version-1.0.0 Bankr developer skill that scaffolds four Bankr Agent API project archetypes: bot, web-service, dashboard, and CLI. Each template ships a typed directory layout with src/ entry points, bankr-client.ts hooks, config.ts, and scripts/run.sh, plus patterns for polling loops, REST routes, HTML dashboards, or Commander.js subcommands. Bot templates target automated trading and price monitors; web-service templates add Express or Fastify endpoints with webhooks and rate limiting; dashboard templates pair a simple public/ frontend with backend API routes; CLI templates use Commander.js for trade, price, and status commands. All templates share package.json, tsconfig.json, .env.example, and .gitignore conventions and defer bankr-client.ts boilerplate to the bankr dev client patterns skill. Developers reach for this skill when starting a new Bankr-integrated repo and need a vetted structure before writing feature code for bots, APIs, dashboards, or terminal tools.
- Starter repo scaffolding
- Env and config conventions
- Sample Bankr API calls
- Faster onboarding
- Consistent project layout
Bankr Dev Project Templates by the numbers
- 353 all-time installs (skills.sh)
- Ranked #1,151 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/bankrbot/claude-plugins --skill bankr-dev---project-templatesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 353 |
|---|---|
| repo stars | ★ 80 |
| Last updated | March 24, 2026 |
| Repository | bankrbot/claude-plugins ↗ |
How do you scaffold a Bankr Agent API project?
Bootstrap a new Bankr-integrated repo with starter structure, env config, sample calls, and conventions so teams skip repetitive setup before writing feature code.
Who is it for?
Developers starting a new Bankr Agent API integration who need to pick and scaffold bot, web-service, dashboard, or CLI repo structure before feature work.
Skip if: Developers who only need bankr-client.ts helpers or endpoint documentation without choosing a full project layout.
When should I use this skill?
User asks to scaffold a Bankr project, create a Bankr bot, web service, dashboard, CLI tool, or needs Bankr project structure guidance.
What you get
Four template directory trees, entry-point code samples, and shared Bankr project config files.
- Project directory tree
- Template entry-point code
- Shared config scaffold files
By the numbers
- Version 1.0.0 skill with 4 project templates: bot, web-service, dashboard, CLI
- Each template defines 6+ scaffold paths including src/, config.ts, and scripts/run.sh
- Requires Node.js 20+ and BANKR_API_KEY per bankr-agent-dev plugin README
Files
Safety & Access Control
Comprehensive safety guidance for using the Bankr API and CLI.
API Key Types
Bankr uses a single key format (bk_...) with capability flags:
| Flag | Controls | Default |
|---|---|---|
agentApiEnabled | /agent/* endpoints | false |
llmGatewayEnabled | LLM Gateway at llm.bankr.bot | false |
readOnly | Restricts agent to read-only tools | false |
Manage flags at bankr.bot/api.
Read-Only API Keys
When readOnly: true, all write tools are filtered from the agent session:
Allowed: Balances, prices, analytics, portfolio, research Blocked: Swaps, transfers, NFT purchases, staking, orders, token launches, leverage, Polymarket bets, claims
The /agent/sign and /agent/submit endpoints return 403 for read-only keys.
IP Whitelisting
Set allowedIps on your API key to restrict usage to specific IPs. Requests from non-whitelisted IPs are rejected with 403.
- Empty array = all IPs allowed (default)
- Non-empty array = only listed IPs can use the key
Dedicated Agent Wallet
When building autonomous agents, create a separate Bankr account rather than using your personal wallet:
- Limited exposure — compromised key only exposes agent wallet funds
- Clear accounting — agent transactions isolated from personal activity
- Independent controls — apply stricter access controls without affecting personal use
- Easy revocation — disable agent account without disrupting primary wallet
Recommended Funding
| Chain | Gas Buffer | Trading Capital |
|---|---|---|
| Base | 0.01-0.05 ETH | As needed |
| Polygon | 5-10 MATIC | As needed |
| Ethereum | 0.05-0.1 ETH | As needed |
| Solana | 0.1-0.5 SOL | As needed |
Rate Limits
| Tier | Daily Limit |
|---|---|
| Standard | 100 messages/day |
| Bankr Club | 1,000 messages/day |
| Custom | Set per API key |
Reset window is 24 hours from first message (rolling), not midnight.
Key Management
- Store keys in environment variables (
BANKR_API_KEY,BANKR_LLM_KEY), never in source code - Add
~/.bankr/and.envto.gitignore - Rotate keys periodically at bankr.bot/api
- Revoke immediately if compromised
- Use separate keys for Agent API vs LLM Gateway if needed
Transaction Safety
- Test first — small amounts on Base/Polygon before scaling
- Verify recipients — double-check addresses before transfers
- Gas buffer — keep enough native tokens for gas
- Immediate execution —
/agent/submitexecutes with no confirmation prompt - Understand calldata — verify trusted source for arbitrary transactions
Pre-Deployment Checklist
- Use a dedicated agent wallet, not your personal account
- Fund with limited amounts appropriate to purpose
- Set read-only if agent only queries data
- Configure IP whitelisting for server-side agents
- Store keys in environment variables
- Test with small amounts first
- Implement error handling for rate limits (429) and access control (403)
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Use project templates to pick and scaffold repo layout; use client patterns for bankr-client.ts code; use api basics for endpoint reference.
FAQ
What Bankr project templates are available?
bankr dev - project templates documents four archetypes—bot, web-service, dashboard, and CLI—each with directory layouts, entry-point patterns, and use cases for automated tasks, HTTP APIs, web UIs, and terminal tools on the Bankr Agent API.
Which template fits a Bankr trading bot?
bankr dev - project templates recommends the bot template for automated trading, price monitors, alert systems, and scheduled tasks, providing a polling-loop index.ts pattern with configurable intervals and graceful shutdown handling.
Where does bankr-client.ts come from?
bankr dev - project templates references the bankr dev client patterns skill for shared bankr-client.ts, package.json, tsconfig.json, .env.example, and .gitignore files that all four templates reuse.