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 agentmods add skills/recca0120/code-quest/fake-summoner-servernpx skills add recca0120/code-quest --skill fake-summoner-servergit clone --depth 1 https://github.com/recca0120/code-questWrote 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/recca0120/code-quest/fake-summoner-server)<a href="https://agentmods.dev/skills/recca0120/code-quest/fake-summoner-server"><img src="https://agentmods.dev/badge/skills/recca0120/code-quest/fake-summoner-server.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 | $0.00065 | $0.03187 |
| Opus 5 | $0.00032 | $0.01594 |
| Sonnet 5 | $0.00013 | $0.00637 |
| Haiku 4.5 | $0.00006 | $0.00319 |
Grade A, and why
fake-summoner-server 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 5d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FakeSummoner — Server Tests
核心概念
FakeSummoner = 一個 測試用的 window/連線,同時擁有:
- 真的 socket.io client(連到測試用 FakeServer)
- 一個 FakeClaude(模擬 CLI 過程)
- FilesystemService / GitService 的記憶體 fake 實作
每個 FakeSummoner 代表「一個 UI window」。多 window 測試建立多個 summoner 共用同一 server。
Import 來源
| 東西 | 從哪 import |
|---|---|
createFakeSummoner / createFakeServer / createTestContainer |
../test/index(server 專用版,會 wire DI container) |
segments as s |
@code-quest/summoner/test |
Server tests 一律從 ../test/index.ts import — 那是包過 DI container 的版本。@code-quest/summoner/test 的同名 export 是 summoner base 版,給 summoner package 本身測試用。
最小 Setup
import { segments as s } from '@code-quest/summoner/test';
import { createFakeSummoner } from '../test/index.ts';
const claude = createFakeSummoner().claude();
const channelId = await claude.initialize();
initialize() 跑完整 CLI 啟動流程:spawn → ready → init segment。
含 DI container(存取 services)
import { createFakeServer, createFakeSummoner, createTestContainer } from '../test/index.ts';
async function setup(sessionId = 'cli-sess') {
const container = createTestContainer();
const server = createFakeServer(container);
const summoner = createFakeSummoner(server);
const claude = summoner.claude();
const channelId = await claude.initialize(s.init(sessionId));
return { container, claude, channelId };
}
FakeSummoner API
const summoner = createFakeSummoner(server);
summoner.claude() // lazy-init FakeClaude
summoner.socket // FakeSocket(注入到 SocketProvider)
summoner.filesystem() // FakeFilesystemService
summoner.git() // FakeGitService(可 undefined)
summoner.openspec() // FakeOpenspecService(可 undefined)
summoner.pluginCli() // FakePluginCliService(可 undefined)
summoner.connected // boolean
summoner.disconnect()
await summoner.send<T>(event, payload) // 透過 socket 送(等 ack)
summoner.receivedEvents() // 收到的所有 server → client events
summoner.receivedEvents('session:init') // 過濾特定 event
summoner.sentEvents() // 所有 client → server emits
summoner.sentEvents('session:launch') // 過濾特定 sent event
summoner.on(event, fn) // subscribe
summoner.holdEmit(event) // 攔截下一次 emit 的 ACK(見下節)
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.
- 5d ago First seen · 338 lines · 65 tokens per session scan A 87bbc2a5c2f9
fake-summoner-server is a skill published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 3,187 once invoked, about $0.0003 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.