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/dvnghiem/flowdeck/python-patternsnpx skills add DVNghiem/FlowDeck --skill python-patternsgit clone --depth 1 https://github.com/DVNghiem/FlowDeckWhat 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.00033 | $0.03204 |
| Opus 5 | $0.00016 | $0.01602 |
| Sonnet 5 | $0.00007 | $0.00641 |
| Haiku 4.5 | $0.00003 | $0.00320 |
Grade A, and why
python-patterns 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 yesterday.
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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Patterns Skill
Idiomatic Python for production-grade code. Covers modern Python 3.10+ practices.
When to Activate
Activate when:
- Writing new Python modules or packages
- Reviewing Python code for correctness and idiom
- Deciding between data modeling approaches (dataclass vs TypedDict vs Pydantic)
- Designing async services or background workers
- Setting up testing infrastructure
Type Hints
Python's type system (PEP 484, 526, 544) makes code self-documenting and enables static analysis with mypy or pyright.
Basic Annotations
# Variables (PEP 526)
count: int = 0
names: list[str] = []
mapping: dict[str, int] = {}
# Functions — always annotate public API
def greet(name: str, times: int = 1) -> str:
return (f"Hello, {name}!\n" * times).rstrip()
# Optional and Union (Python 3.10+ union syntax preferred)
def find_user(user_id: int) -> "User | None":
...
# Use TypeAlias for reused complex types
type UserId = int # Python 3.12+
UserId = NewType("UserId", int) # pre-3.12
Protocols (PEP 544) — Structural Subtyping
Prefer Protocol over ABC when you don't control the implementor.
from typing import Protocol, runtime_checkable
@runtime_checkable
class Serializable(Protocol):
def to_dict(self) -> dict[str, object]: ...
def save(obj: Serializable) -> None:
data = obj.to_dict()
...
# Any class with to_dict() satisfies Serializable — no inheritance required
Generics
from typing import TypeVar, Generic
T = TypeVar("T")
class Stack(Generic[T]):
def __init__(self) -> None:
self._items: list[T] = []
def push(self, item: T) -> None:
self._items.append(item)
def pop(self) -> T:
return self._items.pop()
Data Modeling: Dataclass vs TypedDict vs Pydantic
Choose based on where the data lives and what guarantees you need.
Dataclass — in-memory objects with behavior
from dataclasses import dataclass, field
@dataclass
class Order:
id: str
items: list[str] = field(default_factory=list)
total: float = 0.0
def add_item(self, item: str, price: float) -> None:
self.items.append(item)
self.total += price
# Use @dataclass(frozen=True) for immutable value objects
@dataclass(frozen=True)
class Money:
amount: int # stored in cents
currency: str = "USD"
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.
- yesterday First seen · 535 lines · 33 tokens per session scan A 1797a60f7b97
python-patterns is a skill published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 13d ago), licensed MIT. It adds 33 tokens to every session and 3,204 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
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.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
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…
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.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.