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 liuxinye23/CyberStrikeAI --skill token-lifecycle-reviewgit clone --depth 1 https://github.com/liuxinye23/CyberStrikeAIWrote 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/liuxinye23/cyberstrikeai/token-lifecycle-review)<a href="https://agentmods.dev/skills/liuxinye23/cyberstrikeai/token-lifecycle-review"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/token-lifecycle-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/liuxinye23/cyberstrikeai/token-lifecycle-review"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/token-lifecycle-review.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00828 |
| Opus 5 | $0.00014 | $0.00414 |
| Sonnet 5 | $0.00005 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
token-lifecycle-review 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 10d 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.
What it actually says
Token 生命周期审计
何时使用
当系统使用 JWT、Opaque Token、刷新令牌、长期 API Token、OAuth/OIDC 登录或多端共享凭据时，优先调用本技能。
快速流程
- 明确所有 Token 类型：访问令牌、刷新令牌、一次性票据、设备令牌、Webhook 密钥。
- 记录每类 Token 的签发入口、有效期、续期方式、撤销条件和绑定对象。
- 对登录、刷新、登出、密码变更、权限变更、租户切换后做一致性复测。
- 检查声明、受众、作用域、设备绑定与轮换策略。
重点检查
签发与绑定
- Token 是否绑定正确的用户、租户、设备、客户端类型。
- 是否把高权限信息、内部环境信息、调试字段直接写入声明。
- 多客户端共用同一 Token 体系时，受众和来源是否可区分。
生命周期
- 访问令牌是否过长；刷新令牌是否缺乏轮换与撤销。
- 刷新后旧令牌是否保留过长并发窗口。
- 密码修改、角色变更、账号冻结、MFA 变更后，旧 Token 是否立即失效。
作用域与最小权限
- Scope / role / permissions 是否过宽。
- 不同业务域是否复用同一超大权限令牌。
- 机器到机器 Token 与用户态 Token 是否清晰分离。
传输与存储
- 浏览器端是否把长期 Token 暴露在不必要的位置，例如可被脚本访问的存储。
- 日志、错误响应、调试面板、前端配置中是否泄露真实 Token 值。
建议工具
jwt-analyzer
- 解码头部和载荷，核对
iss、aud、sub、exp、iat、nbf、scope/role 字段。 - 比较普通用户、高权限用户、跨租户用户的声明差异。
http-framework-test
- 复测登录、刷新、登出、权限变化后的关键接口。
- 对“旧 Token + 新状态”的组合进行只读验证，观察是否还被接受。
nuclei
- 作为补充检查默认 OIDC 路径、调试端点、公开元数据、常见暴露接口。
证据要求
- 保存各类 Token 的声明摘要，不要在报告里泄露完整密文。
- 对刷新、撤销、登出前后同一接口做并排对比。
- 明确写出“旧 Token 是否仍可访问什么资源”。
修复建议方向
- 收紧有效期并实施刷新轮换。
- 在密码、MFA、角色与租户切换后统一吊销旧凭据。
- 按客户端类型与业务域拆分 Token 受众和最小权限。
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.
- 10d ago First seen · 100 lines · 27 tokens per session scan A 4a8654bea53e
token-lifecycle-review is a skill published in the GitHub repository liuxinye23/CyberStrikeAI (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 828 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…