Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Elnora-AI/elnora-google-workspace/plugin install google-workspaceWrote 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/elnora-ai/elnora-google-workspace/gw-forms)<a href="https://agentmods.dev/skills/elnora-ai/elnora-google-workspace/gw-forms"><img src="https://agentmods.dev/badge/skills/elnora-ai/elnora-google-workspace/gw-forms/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/elnora-ai/elnora-google-workspace/gw-forms"><img src="https://agentmods.dev/badge/skills/elnora-ai/elnora-google-workspace/gw-forms.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.00108 | $0.01973 |
| Opus 5 | $0.00054 | $0.00986 |
| Sonnet 5 | $0.00022 | $0.00395 |
| Haiku 4.5 | $0.00011 | $0.00197 |
Grade A, and why
gw-forms 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forms
Read and write access to Google Forms via the Forms API v1. Reads are flag-driven (form ID, page size, etc.); writes use a JSON spec file because Forms questions are too schema-heavy for per-question CLI flags.
Invocation
CLI="python3 ${CLAUDE_PLUGIN_ROOT}/cli/gw.py"
Read commands
All read commands accept a form ID or editor URL (https://docs.google.com/forms/d/<FORM_ID>/edit).
Responder URLs (.../forms/d/e/<E_ID>/viewform) are rejected with a clear error — the segment
after /d/e/ is a publication ID, not a form ID, and the API will not accept it.
$CLI forms get FORM_ID --compact
$CLI forms responses FORM_ID [--no-answers] [--page-size N] --compact
$CLI forms response FORM_ID RESPONSE_ID --compact
Write commands
$CLI forms create --title "..." [--description "..."] [--from-json spec.json]
$CLI forms add-items FORM_ID --from-json items.json [--at INDEX]
$CLI forms update-info FORM_ID [--title "..."] [--description "..."]
$CLI forms delete-item FORM_ID INDEX
JSON spec format
--from-json accepts either an array of item specs, or an object {title, description, items}.
Supported item types — every type accepts an optional description and (for questions) required:
// Section divider (forces a new page in the responder UI)
{"type": "section", "title": "About you", "description": "Optional intro text"}
// Short text answer
{"type": "text", "title": "Your name", "required": true}
// Long text answer
{"type": "paragraph", "title": "Tell us more"}
// Equivalent: {"type": "text", "title": "...", "paragraph": true}
// 1–10 (or any range) linear scale
{"type": "linear_scale", "title": "Rate it",
"low": 1, "high": 10, "low_label": "Bad", "high_label": "Great", "required": true}
// Single-choice radio
{"type": "radio", "title": "Your role?",
"options": ["Engineer", "Scientist", "Founder", "Other"], "required": true}
// Multi-select
{"type": "checkbox", "title": "Which apply?", "options": ["A", "B", "C"]}
// Dropdown
{"type": "dropdown", "title": "Pick one", "options": ["A", "B", "C"]}
// Date
{"type": "date", "title": "Event date", "include_time": false, "include_year": true}
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 · 210 lines · 108 tokens per session scan A 2ad720d3b32d
gw-forms is a skill published in the GitHub repository Elnora-AI/elnora-google-workspace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 108 tokens to every session and 1,973 once invoked, about $0.0005 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
managing-google-workspace
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search). Supports MCP tools or CLI via uvx workspace-mcp --cli. Provides tool routing, workflows, and parameter guidance for 114 tools. Triggers for "check my email"…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
alive-cleanup
System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.