[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HA6SBMKRK2C09CKV30N1R":3,"skill-same:01M70HA6SBMKRK2C09CKV30N1R":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M70HA6SBMKRK2C09CKV30N1R","token-card",null,"Render a token-usage stat card from local Claude Code, Codex, Gemini CLI, and OpenCode session logs and commit it into the repository as a file. Use when someone wants a current usage figure in a README, or asks for a shareable card of their coding-agent activity.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftoken-card\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"token card","card","token","community","when","usage","activity","render","as","local","cli","Coding-Agent","opencode","coding","repository","logs","code","commit","gemini cli","gemini","2026-11-10 10:12:30",false,"---\nname: token-card\ndescription: Render a token-usage stat card from local Claude Code, Codex, Gemini CLI, and OpenCode session logs and commit it into the repository as a file. Use when someone wants a current usage figure in a README, or asks for a shareable card of their coding-agent activity.\nmetadata:\n  origin: community\n---\n\n# Token Card\n\nProduce an SVG card summarising this machine's AI coding agent usage — total tokens,\nequivalent API cost, current streak, and the split across agents — and write it into the\nworking tree as a file the README can reference.\n\nThe card is a committed artifact rather than a hosted image, so it renders from the\nrepository itself and does not depend on a third-party endpoint staying up.\n\n## When to Activate\n\n- Someone wants a usage figure visible in a README or docs page.\n- Someone asks for a shareable summary of their agent activity across tools.\n\nUse `\u002Fcost-report` instead when the question is \"what did I spend this week\". The two read\ndifferent sources and produce different things:\n\n| | `\u002Fcost-report` | Token Card |\n|---|---|---|\n| Source | `~\u002F.claude\u002Fmetrics\u002Fcosts.jsonl`, written by ECC's `stop:cost-tracker` hook | The agents' own session logs |\n| Agents | Claude Code | Claude Code, Codex, Gemini CLI, OpenCode |\n| Output | Terminal summary, optional CSV | An SVG file committed to the repo |\n\n## The tool this runs\n\n`@tokenchit\u002Fcli`, MIT licensed: \u003Chttps:\u002F\u002Fgithub.com\u002Fiyashjayesh\u002Ftokenchit>\n\n**Pinned to an exact version, deliberately.** `@latest` resolves to whatever the registry\ncurrently serves, and this tool reads local session logs — so a compromised future release\nwould be executed with access to them before anyone had reviewed it. Pin, and raise the pin\nknowingly:\n\n```bash\nTOKENCHIT_VERSION=0.10.0\n```\n\nTo check the pinned artifact before running it the first time:\n\n```bash\nnpm view @tokenchit\u002Fcli@0.10.0 dist.integrity dist.tarball\n```\n\n## Workflow\n\n1. **Ask before the first download.** `npx` fetches the package from the npm registry and\n   executes it. That is a remote download of code that will read local logs, so get explicit\n   confirmation from the user before the first run on a machine. If they decline, stop here\n   and say what would have run.\n\n2. **Configure, unless this is a dry run.** If `.tokenchit.json` is absent, run:\n\n   ```bash\n   npx -y @tokenchit\u002Fcli@0.10.0 init\n   ```\n\n   It detects which agents have logs on this machine and records them. The file is meant to\n   be committed and never contains a credential.\n\n   **Skip this entirely when the user passed `--dry-run`**, and report that `.tokenchit.json`\n   *would* be created. A preview that writes a config file is not a preview.\n\n3. **Render the card.** The bare command writes to the configured output — `tokenchit.svg`\n   unless `.tokenchit.json` names another path:\n\n   ```bash\n   npx -y @tokenchit\u002Fcli@0.10.0 sync\n   ```\n\n   Append only the flags the user actually asked for, each spelled exactly as below. Do not\n   copy a placeholder into the command — `sync` ignores an unrecognised positional argument\n   rather than refusing it, so a bracketed `[--dry-run]` reaches the CLI as junk and the card\n   is written anyway, which is the opposite of what was asked.\n\n   | Flag | Effect |\n   |---|---|\n   | `--out \u003Cpath>` | Write somewhere other than the configured output |\n   | `--theme auto` \\| `light` \\| `dark` | Card theme; `auto` adapts to the reader's system |\n   | `--dry-run` | Print what would be written and touch nothing |\n\n   `sync` reads local files and sends nothing: no prompts, no code, no file contents leave\n   the machine, and it transmits nothing to any server. The npx invocation around it is a\n   registry download — that is the network access in this workflow, and step 1 is where it\n   is agreed.\n\n4. **Report and offer.** Print the figures it produced — tokens, equivalent cost, streak,\n   per-agent split — and the path written. If the repository has a README that does not yet\n   reference the card, offer to add:\n\n   ```markdown\n   ![tokenchit](.\u002Ftokenchit.svg)\n   ```\n\n   `sync` prints the path relative to the repository root. A Markdown image resolves\n   relative to the file it sits in, so rewrite it for the README being edited: a card at\n   `docs\u002Fusage.svg` is `.\u002Fdocs\u002Fusage.svg` from the root README but `..\u002Fusage.svg` from\n   `docs\u002Fzh-CN\u002FREADME.md`. Pasting the printed path into a nested README points at\n   `docs\u002Fzh-CN\u002Fdocs\u002Fusage.svg` and renders broken.\n\n   Do not edit the README without being asked.\n\nStop after step 4. Publishing to the public leaderboard is a separate `publish` command that\nrequires explicit opt-in, and is not part of this workflow — run it only if the user asks for\nit by name. `unpublish` removes the row and the account again.\n\n## Output\n\nThe path of the SVG, the figures it contains, and the markdown snippet for referencing it.\nOn a dry run: what would have been written, and nothing on disk changed.\n\n## Notes\n\n- Requires Node.js 22 or newer (the package declares `engines: { node: \">=22\" }`). Nothing is\n  installed globally; `npx` fetches the pinned version per run.\n- Reads token counts and timestamps only.\n","# Token Card\n\nProduce an SVG card summarising this machine's AI coding agent usage — total tokens,\nequivalent API cost, current streak, and the split across agents — and write it into the\nworking tree as a file the README can reference.\n\nThe card is a committed artifact rather than a hosted image, so it renders from the\nrepository itself and does not depend on a third-party endpoint staying up.\n\n## When to Activate\n\n- Someone wants a usage figure visible in a README or docs page.\n- Someone asks for a shareable summary of their agent activity across tools.\n\nUse `\u002Fcost-report` instead when the question is \"what did I spend this week\". The two read\ndifferent sources and produce different things:\n\n| | `\u002Fcost-report` | Token Card |\n|---|---|---|\n| Source | `~\u002F.claude\u002Fmetrics\u002Fcosts.jsonl`, written by ECC's `stop:cost-tracker` hook | The agents' own session logs |\n| Agents | Claude Code | Claude Code, Codex, Gemini CLI, OpenCode |\n| Output | Terminal summary, optional CSV | An SVG file committed to the repo |\n\n## The tool this runs\n\n`@tokenchit\u002Fcli`, MIT licensed: \u003Chttps:\u002F\u002Fgithub.com\u002Fiyashjayesh\u002Ftokenchit>\n\n**Pinned to an exact version, deliberately.** `@latest` resolves to whatever the registry\ncurrently serves, and this tool reads local session logs — so a compromised future release\nwould be executed with access to them before anyone had reviewed it. Pin, and raise the pin\nknowingly:\n\n```bash\nTOKENCHIT_VERSION=0.10.0\n```\n\nTo check the pinned artifact before running it the first time:\n\n```bash\nnpm view @tokenchit\u002Fcli@0.10.0 dist.integrity dist.tarball\n```\n\n## Workflow\n\n1. **Ask before the first download.** `npx` fetches the package from the npm registry and\n   executes it. That is a remote download of code that will read local logs, so get explicit\n   confirmation from the user before the first run on a machine. If they decline, stop here\n   and say what would have run.\n\n2. **Configure, unless this is a dry run.** If `.tokenchit.json` is absent, run:\n\n   ```bash\n   npx -y @tokenchit\u002Fcli@0.10.0 init\n   ```\n\n   It detects which agents have logs on this machine and records them. The file is meant to\n   be committed and never contains a credential.\n\n   **Skip this entirely when the user passed `--dry-run`**, and report that `.tokenchit.json`\n   *would* be created. A preview that writes a config file is not a preview.\n\n3. **Render the card.** The bare command writes to the configured output — `tokenchit.svg`\n   unless `.tokenchit.json` names another path:\n\n   ```bash\n   npx -y @tokenchit\u002Fcli@0.10.0 sync\n   ```\n\n   Append only the flags the user actually asked for, each spelled exactly as below. Do not\n   copy a placeholder into the command — `sync` ignores an unrecognised positional argument\n   rather than refusing it, so a bracketed `[--dry-run]` reaches the CLI as junk and the card\n   is written anyway, which is the opposite of what was asked.\n\n   | Flag | Effect |\n   |---|---|\n   | `--out \u003Cpath>` | Write somewhere other than the configured output |\n   | `--theme auto` \\| `light` \\| `dark` | Card theme; `auto` adapts to the reader's system |\n   | `--dry-run` | Print what would be written and touch nothing |\n\n   `sync` reads local files and sends nothing: no prompts, no code, no file contents leave\n   the machine, and it transmits nothing to any server. The npx invocation around it is a\n   registry download — that is the network access in this workflow, and step 1 is where it\n   is agreed.\n\n4. **Report and offer.** Print the figures it produced — tokens, equivalent cost, streak,\n   per-agent split — and the path written. If the repository has a README that does not yet\n   reference the card, offer to add:\n\n   ```markdown\n   ![tokenchit](.\u002Ftokenchit.svg)\n   ```\n\n   `sync` prints the path relative to the repository root. A Markdown image resolves\n   relative to the file it sits in, so rewrite it for the README being edited: a card at\n   `docs\u002Fusage.svg` is `.\u002Fdocs\u002Fusage.svg` from the root README but `..\u002Fusage.svg` from\n   `docs\u002Fzh-CN\u002FREADME.md`. Pasting the printed path into a nested README points at\n   `docs\u002Fzh-CN\u002Fdocs\u002Fusage.svg` and renders broken.\n\n   Do not edit the README without being asked.\n\nStop after step 4. Publishing to the public leaderboard is a separate `publish` command that\nrequires explicit opt-in, and is not part of this workflow — run it only if the user asks for\nit by name. `unpublish` removes the row and the account again.\n\n## Output\n\nThe path of the SVG, the figures it contains, and the markdown snippet for referencing it.\nOn a dry run: what would have been written, and nothing on disk changed.\n\n## Notes\n\n- Requires Node.js 22 or newer (the package declares `engines: { node: \">=22\" }`). Nothing is\n  installed globally; `npx` fetches the pinned version per run.\n- Reads token counts and timestamps only.\n",{"name":5,"metadata":54,"description":7},{"origin":32},"main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Ftoken-card",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill token-card",{"tool":69,"command":70},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill token-card",{"tool":72,"command":73},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill token-card","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftoken-card\u002FSKILL.md",true,[],[78,86,94,101,108,115],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":93},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":93},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":93},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":93},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]