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 ttxttx1111/sts2-llm --skill explain-project-designgit clone --depth 1 https://github.com/ttxttx1111/sts2-llmWrote 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/ttxttx1111/sts2-llm/explain-project-design)<a href="https://agentmods.dev/skills/ttxttx1111/sts2-llm/explain-project-design"><img src="https://agentmods.dev/badge/skills/ttxttx1111/sts2-llm/explain-project-design.svg" alt="Measured on agentmods" 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.00031 | $0.00234 |
| Opus 5 | $0.00015 | $0.00117 |
| Sonnet 5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
explain-project-design 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 7d 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
讲清项目设计
适用场景：向评审、同事、面试官介绍这个仓库。
需要覆盖
- V1：coordinator-heavy 多智能体 runtime
- V2：standalone-bridge runtime
- player / runtime / reviewer 的职责边界
- 为什么第一版 live 路径效果一般
- 为什么第二版 bridge 设计更强
.github标准 Copilot 资产和archive/legacy-runtime-assets/的区别- 为什么这个项目仍然值得写进简历
参考文件
README.mdPROJECT_DESIGN.mdAGENTS.mdSTARTUP.md
约束
- 同时讲清架构故事和真实 live 运维故事。
- 不要把归档的 legacy runtime 资产说成当前活动的标准 Copilot skill。
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.
- 7d ago First seen · 31 lines · 31 tokens per session scan A b58224b45027
explain-project-design is a skill published in the GitHub repository ttxttx1111/sts2-llm (41 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 234 once invoked, about $0.0002 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
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
speckit-init
Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running specify init --integration copilot --integration-options="--skills". USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO…
speckit-bundle
Discover, install, and author Spec Kit bundles via specify bundle. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and…
speckit-extension
Manage Spec Kit extensions via specify extension. USE FOR: installing/removing/updating spec-kit extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting extension resolution priority, managing extension catalogs. DO NOT USE FOR: presets (use speckit-preset), bundles…
speckit-preset
Manage Spec Kit presets via specify preset. USE FOR: installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting preset resolution priority, managing preset catalogs. DO NOT USE FOR: extensions (use…
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…