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 DavidROliverBA/ArchitectKB --skill form-statusgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/form-status)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/form-status"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/form-status.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.00006 | $0.00873 |
| Opus 5 | $0.00003 | $0.00436 |
| Sonnet 5 | $0.00001 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
form-status 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 8d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/form-status Skill
Show status of form submissions across projects.
Usage
/form-status # All forms summary
/form-status pending # Forms awaiting response
/form-status overdue # Forms past expected response
/form-status MyDataIntegration # Forms for specific project
/form-status DPIA # All DPIA submissions
/form-status CyberRisk # All Cyber Risk assessments
Instructions
-
Search for FormSubmission notes:
Glob pattern: **/Form Submission*.md Also check: type = "FormSubmission" in frontmatter -
Extract metadata from each:
- formType (DPIA, CyberRisk, ChangeRequest, TPRM, IAF, Other)
- status (draft, submitted, pending, approved, rejected, expired)
- project
- submittedDate
- responseDate
- expiryDate
- requestingTeam
-
Apply filter if provided:
- "pending" = status is "submitted" or "pending"
- "overdue" = submittedDate > 30 days ago AND status not in [approved, rejected]
- Project name = matches project field
- Form type = matches formType field
-
Generate report:
# Form Submission Status
**Generated**: {{date}}
**Filter**: {{filter or "All"}}
## Summary
| Status | Count |
|--------|-------|
| Draft | X |
| Submitted/Pending | X |
| Approved | X |
| Rejected | X |
| Expired | X |
## By Form Type
### DPIA (Data Protection Impact Assessment)
| Project | Status | Submitted | Response | Reference |
|---------|--------|-----------|----------|-----------|
| [[Project]] | pending | 2026-01-05 | - | DPIA-123 |
### CyberRisk (Cyber Security Risk Assessment)
| Project | Status | Submitted | Response | Reference |
|---------|--------|-----------|----------|-----------|
### TPRM (Third Party Risk Management)
...
### ChangeRequest
...
### IAF (Initial Assessment Form)
...
## Attention Required
### Overdue (>30 days, no response)
- [[Form Submission - DPIA for MyDataIntegration]] - submitted 2025-12-01 (41 days ago)
### Expiring Soon (<30 days to expiry)
- [[Form Submission - TPRM for MaintenanceSystem]] - expires 2026-02-10
### Drafts Not Submitted
- [[Form Submission - CyberRisk for OpDef]] - created 2026-01-03
## By Project
### [[Project - MyDataIntegration]]
- DPIA: approved (2025-11-15)
- CyberRisk: pending (submitted 2026-01-05)
- TPRM: draft
### [[Project - MaintenanceSystem]]
...
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.
- 8d ago First seen · 140 lines · 6 tokens per session scan A 25bdce5664b3
form-status is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 873 once invoked, about $0.0000 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.