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 reluctantfuturist/loyal-wingman --skill query-contextgit clone --depth 1 https://github.com/reluctantfuturist/loyal-wingmanWrote 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/reluctantfuturist/loyal-wingman/query-context)<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/query-context"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/query-context/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/reluctantfuturist/loyal-wingman/query-context"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/query-context.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.00042 | $0.01272 |
| Opus 5 | $0.00021 | $0.00636 |
| Sonnet 5 | $0.00008 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
query-context 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Context
The Iron Law
SEARCH COMPREHENSIVELY. Never invent missing information - identify gaps for user decision.
When to Use
- Before drafting any scene (called by writing-mode)
- When user asks "what do we know about X"
- To verify continuity with existing canon
The Process
Phase 1: Identify Search Targets
From scene requirements, list:
- Characters involved
- Locations featured
- Equipment used
- Factions relevant
- Systems/magic elements
- Themes being explored
- Timeline context needed
- Previous scenes for continuity
Phase 2: Search Vault
Search ALL world bible folders:
-
Characters -
02_World/Characters/- Current status, relationships, equipment
- Recent events affecting character
-
Locations -
02_World/Locations/- Physical description, special properties
- Previous events at location
-
Equipment -
02_World/Equipment/- Technical specifications
- Special properties, behaviors
-
Factions -
02_World/Factions/- Structure, key members
- Current status, goals
-
Systems -
02_World/Systems/- Rules and costs
- Mechanics and limitations
- Character abilities
-
Themes -
02_World/Themes/- Core thematic elements
- Moral framework
-
Timeline -
02_World/Timeline_Events/- Relevant historical events
- Political/social backdrop
-
Project scenes -
10_Projects/[Project]/Scenes/- Continuity with earlier chapters
- Foreshadowing requirements
-
Research -
03_Research/- Cultural authenticity
- Technical accuracy
-
Plot Threads - Project index
## Plot Threads- Active threads for this scene
- Stale/orphaned thread warnings
REQUIRED SUB-SKILL: Invoke plot-threads (Query mode)
Phase 3: Compile Findings
Format results as:
## Context for [Scene Description]
### Available Canon
**Characters:**
- [Name]: [relevant state/equipment/relationships] (source: file)
**Location:**
- [Name]: [key details] (source: file)
**Factions:**
- [Name]: [relevant involvement] (source: file)
**Systems:**
- [System]: [applicable rules/costs] (source: file)
**Themes:**
- [Theme]: [how it applies] (source: file)
**Timeline:**
- Scene takes place: [date/period]
- Relevant backdrop: [events]
**Equipment:**
- [Item]: [specs needed for scene] (source: file)
### Gaps Identified
- [Gap 1]: No vault entry found. Need user decision.
- [Gap 2]: Contradictory information in [file1] vs [file2].
### Research Needs
- [Topic]: Needs external research (flag for research)
### Continuity Flags
- Previous scene: [summary of state to maintain]
- Future scene: [setup requirements]
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 · 177 lines · 42 tokens per session scan A b7bce66ebf06
query-context is a skill published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 42 tokens to every session and 1,272 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-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…