Borrowing it
Nothing to install: this file belongs to QuickerHub/quicker-rpc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/QuickerHub/quicker-rpc/main/.cursor/skills/quicker-rpc-publish/SKILL.mdgit clone --depth 1 https://github.com/QuickerHub/quicker-rpcWrote 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/quickerhub/quicker-rpc/quicker-rpc-publish)<a href="https://agentmods.dev/skills/quickerhub/quicker-rpc/quicker-rpc-publish"><img src="https://agentmods.dev/badge/skills/quickerhub/quicker-rpc/quicker-rpc-publish/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/quickerhub/quicker-rpc/quicker-rpc-publish"><img src="https://agentmods.dev/badge/skills/quickerhub/quicker-rpc/quicker-rpc-publish.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.00106 | $0.02838 |
| Opus 5 | $0.00053 | $0.01419 |
| Sonnet 5 | $0.00021 | $0.00568 |
| Haiku 4.5 | $0.00011 | $0.00284 |
Grade A, and why
quicker-rpc-publish 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quicker-rpc 公开发布
版本号必守：getquicker 上传 必须第三段 +1、revision→0；
version.json只能递增、禁止减小。细则：.cursor/skills/quicker-qkbuild-version-publish/SKILL.md。禁止仅用-trevision 就当「已发布」。
完整流程（Agent 顺序）
- 若本次或近期改过
agent-gui/llm-publish.config.json：先 发布 publish config —pwsh -NoProfile -File ./publish/Sync-LlmPublishConfig.ps1（quicker-agent-llm-apikey-config//publish-llm-config），确保BUNDLED_LLM_CONFIG+ Bitiful OSS 与本地一致 git status；读取 baseline（最新 tag + 已提交version.json）；第三段 +1 bumpversion.json（第四段 →0），且 必须大于 baseline；commit — 见quicker-qkbuild-version-publishgit log自上一 tag → 撰写 changelog → 写入publish/changelogs/vX.Y.Z.md并 commitpwsh ./publish/Publish-GitHubRelease.ps1 -WaitForCi→ 默认并行：后台启动本地 Electron 预检 + 立即 push tag 触发 CI。本地日志通常先报错，优先按%TEMP%\qkrpc-preflight-vX.Y.Z.log修复；CI 失败可暂忽略。修复后-ForceRetag重发。- 仅本地阻塞预检：
Test-QuickerAgentReleaseBuild.ps1或-PreflightBeforeTag - 跳过预检：
-SkipPreflight；结束后等待本地结果：-WaitForPreflight
- 仅本地阻塞预检：
.github/workflows/release-cli.yml在 GitHub Actions 编译 qkrpc zip/setup 与 QuickerAgent Electron 安装包并发布 Release（-WaitForCi等待完成；CI 失败时仍会打印本地预检日志路径）。仅 Release 上传失败：Actions Run workflow →pipeline=release-only+artifact_run_id（见publish/release-cli-ci.md）；NSIS/编译失败用-ForceRetag全量重编pwsh ./build.ps1 -Publish -NoVersion→ Quicker 依赖 quicker.rpc 上传（版本与version.json一致，不再 bump）qkrpc action list --limit 1 --json确认插件在线（或已qkrpc serve且/health为 ok）qkrpc action update --id f5c76108-3ce9-433f-8cd0-8f0d9c562052 --changelog-file publish/changelogs/vX.Y.Z.md --json- QuickerAgent 动作页（getquicker）：
page.html用占位符{{QUICKER_AGENT_SEMVER}}（勿手写版本号）。本地 Bitiful 上传后执行：- 推荐：
pwsh ./publish/Publish-GitHubRelease.ps1 -WaitForCi（CI 结束后自动本地上传 Bitiful →Sync-QuickerAgentActionDoc.ps1 -Push） - 或手动：
pwsh ./publish/Upload-QuickerAgentToBitiful.ps1 -Tag vX.Y.Z，再Sync-QuickerAgentActionDoc.ps1 -Push - 需在 quicker-agent 兄弟仓库（或
QUICKER_AGENT_REPO）；Bitiful 凭证见publish/.env.example（复制为publish/.env）
- 推荐：
- 汇报 Release URL、Quicker 包版本、action update / 动作页 sync 结果、用户安装命令
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.
- 11d ago First seen · 108 lines · 106 tokens per session scan A c5dc01c1aa02
quicker-rpc-publish is a skill published in the GitHub repository QuickerHub/quicker-rpc (13 stars, last pushed 27d ago), licensed MIT. It adds 106 tokens to every session and 2,838 once invoked, about $0.0005 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-30.
Other skills, from other repositories
atmos-vendoring
Component vendoring: vendor.yaml and component.yaml manifests, immutable vendor.lock.yaml receipts, pulling from Git/S3/HTTP/OCI/Terraform Registry, --stack/--labels/--tags selector composition, native vendor update, clean, diff, config, and reviewed local component copies.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts.
git-revert-safety
Apply when reverting commits, undoing merges, or recovering from branch contamination. Covers collateral damage verification (manifest, package.json, CHANGELOG, lockfiles), cherry-pick vs revert decision matrix, partial-revert detection, merge-parent handling, and post-revert CI verification. Prevents the most common…
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.