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 commands/gregpriday/ask-google-mcp/releasegit clone --depth 1 https://github.com/gregpriday/ask-google-mcpWhat 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.00008 | $0.01732 |
| Opus 5 | $0.00004 | $0.00866 |
| Sonnet 5 | $0.00002 | $0.00346 |
| Haiku 4.5 | $0.00001 | $0.00173 |
Grade A, and why
release 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automated NPM Release for @gpriday/ask-google-mcp
Publishing is handled by the .github/workflows/publish.yml workflow, which runs on every v* tag push using NPM trusted publishing (OIDC). This command prepares and pushes the tag; CI does the actual npm publish.
Current State
- Git status: !
git status - Current branch: !
git branch --show-current - Latest tag: !
git describe --tags --abbrev=0 2>/dev/null || echo "none" - Current version: !
node -p "require('./package.json').version" - Changes since last tag: !
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD")..HEAD --oneline 2>/dev/null || echo "No previous tags"
Automated Release Process
This command will automatically:
- Analyze commit history to determine version bump type
- Run all tests locally (STOP if any fail)
- Update
package.jsonversion - Commit the bump
- Create an annotated git tag
- Push
mainand the tag to origin - Watch the publish workflow and report when it publishes
Step 1: Analyze Changes & Determine Version
Version bump override: $ARGUMENTS
If $ARGUMENTS is empty, auto-detect version bump:
Read all commits since the last git tag. Analyze commit messages following Conventional Commits:
- MAJOR (breaking): Look for "BREAKING CHANGE:", "!" after type (e.g., "feat!:"), or "major:" prefix
- MINOR (feature): Look for "feat:", "feature:", new functionality
- PATCH (fix): Look for "fix:", "bugfix:", "chore:", "docs:", "refactor:", "test:", "style:", improvements
Rules:
- If any BREAKING CHANGE found → MAJOR bump
- If any feat/feature found (no breaking) → MINOR bump
- Otherwise → PATCH bump
- If no commits since last tag → Ask user if they want to proceed with PATCH
Calculate new version based on current package.json version and bump type.
Step 2: Pre-Release Validation
- Check for uncommitted changes
- Run
git status --porcelain - If ANY uncommitted changes exist, STOP and tell the user: "Please commit or stash all changes before running release. The release process will only commit the version bump in package.json."
- Run
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 · 183 lines · 0 tokens per session scan A 407ff4f03cac
release is a command published in the GitHub repository gregpriday/ask-google-mcp (1 stars, last pushed 18d ago), licensed MIT. It adds 8 tokens to every session and 1,732 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.