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 DVNghiem/FlowDeck --skill context-guardgit clone --depth 1 https://github.com/DVNghiem/FlowDeckWrote 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/dvnghiem/flowdeck/context-guard)<a href="https://agentmods.dev/skills/dvnghiem/flowdeck/context-guard"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/context-guard/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/dvnghiem/flowdeck/context-guard"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/context-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 83 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00028 | $0.01418 |
| Opus 5.5 | $0.00011 | $0.00567 |
| Sonnet 5.5 | $0.00006 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
context-guard 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 1mo 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Guard Skill
Defines the protected-pattern contract: a whitelist of files, tools, decisions, and messages that must survive context compaction.
What Is a Protected Pattern?
A protected pattern is any context item that a pruning pass must skip. Without it, compaction can silently discard the very state an agent needs to finish a task.
Four categories:
Tool Patterns
Tool invocations that must remain in the conversation window while they are in flight or unverified. Example: a write or edit call whose result has not yet been confirmed.
File Patterns
Paths that anchor the current session. These include active planning files, project conventions, and safety ledgers.
Decision Records
Records that explain why the session is in its current state. Removing them forces the agent to re-derive intent from scratch.
Intent Anchors
User messages that establish the original goal and the most recent steering corrections. These are the cheapest way to prevent drift.
Default Protected-Pattern Registry
FlowDeck ships with a default registry. Override it in .opencode/flowdeck/protected-patterns.yaml, never by editing this skill.
System Files
| Pattern | Reason |
|---|---|
AGENTS.md |
Operating rules for every agent |
~/.fd-plan/<slug>/STATE.md |
Current phase, completed steps, blockers |
~/.fd-plan/<slug>/<topic>/plan.md |
Active plan and success criteria |
Safety Files
| Pattern | Reason |
|---|---|
~/.fd-plan/<slug>/.codebase/DECISIONS.jsonl |
Decision ledger — why choices were made |
~/.fd-plan/<slug>/.codebase/FAILURES.json |
Failure replay engine data |
Intent Anchors
| Pattern | Reason |
|---|---|
| Last 2 user messages | Original goal + latest steering |
| Current phase objective | From STATE.md — the single sentence that defines success |
Active Operations
Any pending tool whose side effects have not been verified:
| Tool | Condition |
|---|---|
write |
while pending verification |
edit |
while pending verification |
bash |
while exit code/output not yet checked |
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.
- 1mo ago First seen · 173 lines · 28 tokens per session scan A 42edd00fe630
context-guard is a skill published in the GitHub repository DVNghiem/FlowDeck (39 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,418 once invoked, about $0.0001 per session on Opus 5.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
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
simplify
Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.