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/open-curiosity/gini-agent/google-formsnpx skills add Open-Curiosity/gini-agent --skill google-formsgit clone --depth 1 https://github.com/Open-Curiosity/gini-agentWrote 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/open-curiosity/gini-agent/google-forms)<a href="https://agentmods.dev/skills/open-curiosity/gini-agent/google-forms"><img src="https://agentmods.dev/badge/skills/open-curiosity/gini-agent/google-forms.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 | $0.00019 | $0.02408 |
| Opus 5 | $0.00010 | $0.01204 |
| Sonnet 5 | $0.00004 | $0.00482 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
google-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 4d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Forms
Use gws forms to create new forms, add questions to them, change publish settings, and read submitted responses. Wraps the Forms v1 API.
Prerequisites
- If this deployment is managed/hosted, the Google credential is already provisioned at sign-in —
gwsis installed and authenticated, so skip the setup flow below and rungwsdirectly. Scopes are fixed at sign-in on a managed deployment: when a call fails withscope requiredor HTTP 401, tell the user which action needs a scope their account wasn't granted, instead of trying to set anything up. (The scope list below still describes which verb needs which scope.) gwsinstalled and authenticated. Ifgwsis not on PATH ORgws auth statusreports no authenticated user, do NOT silently call setup. Instead, in a single short reply to the user:- State plainly what's missing — e.g. "Google Workspace access isn't set up on this machine yet" or "your Google sign-in has expired."
- Ask one sentence: "Want me to walk you through setting it up?" Wait for the user's answer.
- If they say yes, call
read_skillwith namegoogle-workspace-setupand run that skill's onboarding flow turn-by-turn. If they say no or ask to defer, acknowledge briefly and stop — do not retry the original request.
- Apply the same flow when any
gws forms ...call fails mid-task withcommand not found/ ENOENT, HTTP 401, "no credentials", or "scope required". Don't report the failure as a dead end — surface the missing prerequisite and ask if the user wants to set it up before moving on. - OAuth scopes the user picked at login must cover the verbs the agent will use:
- Create / edit forms (read + write structure):
forms.body - Read form structure only (e.g. mapping
questionId → titlefor summaries):forms.body.readonly - Read submitted responses:
forms.responses.readonly - Summarize responses by question text:
forms.responses.readonlyANDforms.body.readonly(orforms.body).forms.responses.readonlyis NOT onforms.get's authorized scope list — you need a body scope to fetch the structure separately. - The Forms API also accepts the broader
drivescope for create, get, and responses — an account with a fulldrivegrant can edit form structure and read responses without the separate Forms scopes.
- Create / edit forms (read + write structure):
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.
- 4d ago First seen · 189 lines · 19 tokens per session scan A d9b37c33acca
google-forms is a skill published in the GitHub repository Open-Curiosity/gini-agent (1,869 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 2,408 once invoked, about $0.0001 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
gno
Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs…
vibelution-continuous-optimization-loop
Runs one evidence-driven Vibelution optimization iteration from the ROI backlog: pick one todo item, worktree isolate, implement, machine-verify, merge, update STATE. Use when the user starts /loop for project improvement, continuous optimization, or agent-dev ROI backlog work.
personal-assistant
Use this skill whenever the user acts like Bamboo is their personal assistant. Triggers include stating commitments, deadlines, appointments, or recurring routines ("remind me to...", "I need to... by Friday", "every Monday I..."), asking to be reminded of something, agenda questions ("what's on my plate", "what's due…
review
Review code changes, pull requests, patches, or a scoped code area for actionable correctness, security, compatibility, and test risks with file and line evidence. Use for review or audit requests; do not use for general proofreading, feature implementation, or debugging a reported failure when the user wants a fix.
debug
Diagnose a concrete failure, regression, crash, hang, flaky test, or incorrect runtime behavior by reproducing it, testing hypotheses, and identifying the evidence-backed root cause. Use when symptoms or failing output exist; do not use for feature implementation without a failure, general code review, or a conceptual…
plan
Build an executable implementation, migration, or rollout plan from read-only repository exploration, including constraints, dependencies, ordered changes, verification, risks, and rollback points. Use when the user asks for a plan or decomposition before implementation; do not use when they want a small change…