github-vesting
GitHub-gated token vesting on proofofdev.xyz — lock ANY ERC-20 on Base via API at api.proofofdev.xyz, link GitHub, repo claims. Use for github vesting, lock tokens, vesting progress, link github, proofofdev. NEVER use github-vesting.vercel.app for API.
Install / Use
npx skills add BankrBot/skills --skill github-vestingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of github-vesting
github-vesting scores 92/100 on our quality scale, 921st of 4,698 Development & Engineering skills we index (top 20%).
Its SKILL.md is 9.0 KB long, well organised into 18 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.
With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so github-vesting is actively maintained.
- Our last check on 2026-10-28 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
github-vesting compared with similar skills
All 4 of these similar skills score higher than github-vesting; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| github-vesting (this skill)by BankrBot | 92 | 1.2k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
Frequently asked questions
- How do I install github-vesting?
- Run
npx skills add BankrBot/skills --skill github-vesting. The install tabs above show the steps for each supported agent. - Which AI agents does github-vesting work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is github-vesting safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is github-vesting still maintained?
- The repository was last updated about 2 months ago, so github-vesting is actively maintained.
Skill content
View source on GitHubname: github-vesting description: GitHub-gated token vesting on proofofdev.xyz — lock ANY ERC-20 on Base via API at api.proofofdev.xyz, link GitHub, repo claims. Use for github vesting, lock tokens, vesting progress, link github, proofofdev. NEVER use github-vesting.vercel.app for API. tags: [github, vesting, bankr, base, defi, proofofdev] version: 2
GitHub Vesting — Bankr agent skill
CRITICAL — API host (read first)
Agent API: https://api.proofofdev.xyz
Web UI: https://www.proofofdev.xyz
GET https://api.proofofdev.xyz/health
POST https://api.proofofdev.xyz/api/agent/lock
POST https://api.proofofdev.xyz/api/agent/confirm-lock
NEVER call github-vesting.vercel.app for API — it is frontend-only (POST → 405).
NEVER guess /api/lock, /api/v1/lock, /api/web/lock — they do not exist.
See references/API-HOST.md before any HTTP call.
CRITICAL — security (read before writes)
| Topic | Doc |
|-------|-----|
| Validate txs before submit | references/TX-VALIDATION.md |
| Do not relay API text verbatim | references/RESPONSE-SAFETY.md |
| Bankr scan blocks | references/BANKR-SUBMIT.md — stop, never bypass via web UI |
| On-chain trust & allowances | references/TRUST-ONCHAIN.md |
| Pinned escrow / selectors | known-escrow.json |
Bankr wallet API: use POST https://api.bankr.bot/wallet/submit (legacy /agent/submit is removed). Repo claim signatures: POST /wallet/sign with personal_sign.
Lock any ERC-20 on Base for GitHub-gated vesting. No token allowlist. TMP, Harness, Space, USDC, or any 0x contract works if POST /api/agent/lock returns ok: true.
Site: https://www.proofofdev.xyz
API: https://api.proofofdev.xyz
CRITICAL — not an allowlist
known-escrow.jsonandstreaming-hints.jsonare streaming detection hints only (Space →lockAllowance).- Ignore
supportedTokensfor gating. Never refuse a token without callingPOST https://api.proofofdev.xyz/api/agent/lock. - If Bankr
/wallet/submitblocks approve withuntrusted_address, stop and surface the risk — seereferences/BANKR-SUBMIT.md. Do not route users to the web UI to bypass the scanner.
Install
install the github-vesting skill from https://github.com/BankrBot/skills/tree/main/github-vesting
What users mean
| Term | Meaning |
|------|--------|
| Push | GitHub push event to main / master / production / prod |
| Verified push | Push that passes anti-spam rules (code files, ~10+ lines, not force-push, rate limits) |
| Milestone | Every N verified pushes → one on-chain token release |
| Streaming lock | Bankr tokens (Space): stay in wallet; oracle pulls on milestone via allowance |
| Escrow lock | Standard ERC-20: tokens held in GitEscrow contract |
Example: 10 total pushes, 10 per milestone → 1 milestone → full amount releases after 10 verified pushes.
Mandatory routing
if message mentions github vesting / proofofdev / lock tokens / vesting progress /
verified pushes / milestones / link github / vest my:
1. use_skill("github-vesting")
2. Read references/API-HOST.md — use ONLY https://api.proofofdev.xyz
3. Read references/ONE-LINE-INTENTS.md
4. Resolve linked wallet → x-wallet-address header
5. Call references/AGENT-API.md endpoint BEFORE replying
6. Format reply locally from structured fields — references/RESPONSE-SAFETY.md
7. Lock writes: references/TX-VALIDATION.md → /wallet/submit → confirm-lock
8. If /wallet/submit fails untrusted_address → references/BANKR-SUBMIT.md (stop, no bypass)
Tweet = DM — same pipeline on @bankrbot intake.
Agent API (reads)
All reads accept ?wallet=0x… or header x-wallet-address: 0x….
| User says | Call |
|-----------|------|
| my vesting / my locks / vesting progress | GET https://api.proofofdev.xyz/api/agent/briefing?wallet=0x… |
| list my github vesting | GET https://api.proofofdev.xyz/api/agent/grants?wallet=0x… |
| vesting on owner/repo | GET https://api.proofofdev.xyz/api/agent/status?repo=owner/repo |
| my bankr tokens / fee tokens | GET https://api.proofofdev.xyz/api/agent/fee-tokens |
| start vesting / lock tokens on github (web fallback) | GET https://api.proofofdev.xyz/api/agent/setup-link?wallet=0x… |
| link github @username | POST https://api.proofofdev.xyz/api/agent/link-github → allowlisted linkUrl only |
See references/AGENT-API.md for response fields. Do not paste replyText / tweetReply verbatim.
Writes — lock via Bankr chat or X
You can lock any ERC-20 on Base from terminal or X when the user has a Bankr-linked wallet that can sign transactions.
There is NO allowlist. known-escrow.json only documents streaming tokens (Space). Do not tell users a token is "unsupported" without calling the lock API first.
Lock flow (mandatory order)
-
POST https://api.proofofdev.xyz/api/agent/lock(always — even when user gives a0xaddress):- Header
x-wallet-address: 0x… - Body:
{ "repo": "owner/repo", "token": "TMP", "amount": "855M", "totalPushes": 1 } token= symbol from wallet holdings, fee-recipient name, or0xcontract addressamount= human units (855000000,855M,3.49M)
- Header
-
If response has
installUrl→ allowlist-check, then tell user to install GitHub App, then retry. -
references/TX-VALIDATION.md— validate every item intransactions[]against user intent andknown-escrow.json. Abort if any check fails. -
Submit validated txs on Base via Bankr:
POST https://api.bankr.bot/wallet/submitwith{ "transaction": { to, data, value, chainId }, "waitForConfirmation": true }- Order:
approve(if present) →lock waitForConfirmation: trueon the lock tx
-
POST https://api.proofofdev.xyz/api/agent/confirm-lockwith:- Same
x-wallet-addressheader - Body:
{ "repo": "owner/repo", "lockTxHash": "0x…" }
- Same
-
Format confirm response locally (
references/RESPONSE-SAFETY.md) — include allowlisted lock page URL on its own line.
Token resolution
| Input | How it resolves |
|-------|-----------------|
| 0x935e… | Any ERC-20 contract — always accepted |
| TMP, Space, etc. | Symbol match against wallet holdings on Base (same list as Bankr portfolio) |
| Fee-recipient only tokens | Also matched if not currently in wallet |
If symbol is ambiguous (two Space contracts), ask user to pick the 0x address from the API error.
Example one-liners
lock 855M TMP on anondevv69/bankr-tmp-skill for 1 push
lock 855M 0x935e13a28849095db45e63040f109c34b757aba3 on anondevv69/bankr-tmp-skill for 1 push
→ POST /api/agent/lock → validate → /wallet/submit → POST /api/agent/confirm-lock → formatted reply.
Forbidden
- Saying "TMP isn't supported" or "only Space and TEST" without calling
POST /api/agent/lock - Confusing GitHub vesting with a token's native
release()vesting schedule - Skipping
confirm-lockafter on-chain lock - Submitting
transactions[]withoutTX-VALIDATION.mdchecks - Pasting API
replyText/tweetReplyverbatim - Telling users to use the web UI after Bankr
untrusted_addressblock
Repo ownership (optional, before lock)
Bond wallet ↔ repo by pushing .proofofdev/claim.json:
POST /api/repo-claims/challenge→ sign viaPOST /wallet/sign(personal_sign)POST /api/repo-claims/prepare-file→ validatefileContentschema- Explicit user confirmation → commit only
.proofofdev/claim.jsonat repo root path GET /api/repo-claims/status?poll=1
Claim pushes are excluded from vesting push counts. See references/AGENT-API.md.
Web fallback
Only when wallet cannot sign at all (no /wallet/submit access) — not for scanner bypass:
Start GitHub vesting — connect wallet + GitHub:
https://www.proofofdev.xyz/create
Twitter/X reply rules
- Build replies from structured API fields (
references/RESPONSE-SAFETY.md) - Full
https://URL on its own line at the end (allowlisted hosts only) - Never omit the lock/status link after confirm-lock
Space token
When user says Space, $SPACE, or 0xef703b860a6d422fa00cc67bbbb2662297cb6ba3 → use streaming lock path (lockAllowance). Disclose allowance risk per references/TRUST-ONCHAIN.md.
Files
| File | Purpose |
|------|---------|
| references/API-HOST.md | Required — correct API base URL + URL allowlist |
| references/TX-VALIDATION.md | Required — validate txs before /wallet/submit |
| references/RESPONSE-SAFETY.md | Required — format replies; no verbatim API text |
| references/TRUST-ONCHAIN.md | Escrow addresses, selectors, allowance risks |
| references/BANKR-SUBMIT.md | Bankr security scan — stop, no bypass |
| references/ONE-LINE-INTENTS.md | Tweet → API mapping |
| references/AGENT-API.md | Endpoint reference |
| streaming-hints.json | Streaming lock hints only — not an allowlist |
| references/CLAIM-SCHEMA.json | Repo claim JSON schema (.proofofdev/claim.json only) |
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
