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 Effulgent-Point/paw --skill architecturegit clone --depth 1 https://github.com/Effulgent-Point/pawWrote 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/effulgent-point/paw/architecture)<a href="https://agentmods.dev/skills/effulgent-point/paw/architecture"><img src="https://agentmods.dev/badge/skills/effulgent-point/paw/architecture.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.00000 | $0.00341 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
architecture 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 6d 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
Architecture Skill
When to use: Designing systems, evaluating tradeoffs, deciding component boundaries, planning integration points.
How to decompose
- Identify boundaries — where does data enter and leave? Each boundary is a potential component edge.
- Map data flow — follow the request from user action to database and back. Every hop is an integration point.
- Identify integration points — external APIs, databases, message queues, file systems. Each is a failure point.
- List risks — what can go wrong at each boundary and integration point?
When to split vs combine
Split when:
- Two things change for different reasons (separate concerns)
- Two things deploy on different schedules
- One thing needs to scale independently
Combine when:
- Split would require synchronous communication between the halves
- Both change together almost every time
- The boundary is speculative ("we might need this someday")
Risk assessment framework
For each risk, assess:
| Low Impact | High Impact | |
|---|---|---|
| High Likelihood | Monitor | Mitigate now |
| Low Likelihood | Accept | Plan mitigation |
Every risk needs: description, likelihood, impact, and mitigation strategy.
Presenting alternatives
Always present 2+ approaches:
- Approach A — pros, cons, estimated effort, risk profile
- Approach B — pros, cons, estimated effort, risk profile
- Recommendation — which and why, stated tradeoff
Never present one option as the only option. The point of alternatives is to show you considered the space.
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.
- 6d ago First seen · 43 lines · 0 tokens per session scan A cbc0d140e607
architecture is a skill published in the GitHub repository Effulgent-Point/paw (2 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 341 tokens. 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
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.
jk
Jenkins CLI for controllers. Use when users need to manage jobs, pipelines, config.xml, runs, logs, artifacts, credentials, nodes, or queues in Jenkins. Triggers include "jenkins", "jk", "pipeline", "build", "job create", "job config", "config.xml", "run logs", "jenkins credentials", "jenkins node".
push
Operate a Push personal assistant, inspect its health and jobs, and author or validate Push job runbooks. Use when a request concerns Push setup, CLI commands, assistant files, scheduled jobs, or delivery behavior.
ground-state
Before starting any non-trivial implementation, run a pre-flight reconnaissance pass to triangulate git state, project infrastructure, and prior-session memory. Auto-assembles a verified grounding preamble — a session-scoped artifact the orchestrator pastes verbatim into every subsequent sub-agent brief — eliminating…
hatch3r-board-refresh
Regenerates the living board overview dashboard from current board state. Scans all open issues, computes health metrics, and updates the meta:board-overview issue.