claude-codex-settings is a collection of configurations and reusable extensions for Claude Code, OpenAI Codex, Cursor, and related coding tools. Developers use its skills, commands, hooks, agents, plugins, and MCP servers to shape coding-agent workflows and connect alternative model APIs. The catalogue entries are components of this collection that can be installed into supported coding tools.
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 fcakyon/claude-codex-settings --skill google-telemetrygit clone --depth 1 https://github.com/fcakyon/claude-codex-settingsWrote 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/fcakyon/claude-codex-settings/google-telemetry)<a href="https://agentmods.dev/skills/fcakyon/claude-codex-settings/google-telemetry"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/google-telemetry/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/fcakyon/claude-codex-settings/google-telemetry"><img src="https://agentmods.dev/badge/skills/fcakyon/claude-codex-settings/google-telemetry.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.00058 | $0.01273 |
| Opus 5.5 | $0.00023 | $0.00509 |
| Sonnet 5.5 | $0.00012 | $0.00255 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
google-telemetry 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google telemetry
Use google-analytics-cli and google-search-console-cli as JSON wrappers around Google's APIs. Use raw official API calls for a reporting method the CLIs lack. Keep this workflow independent of the app's framework. Do not configure MCP.
Pick the source
- GA4 measures instrumented visits and product events. Inspect the event's caller before interpreting what it proves.
- Search Console measures Google Search exposure and clicks. It cannot identify extension versions, signed-in users or successful playback.
- Saved submissions, entitlements and completed transactions belong to the application's database. A GA submit event may fire before the write succeeds.
- Deployment status and active SHA belong to the hosting platform. Traffic cannot prove which revision is serving without a recorded version dimension.
Discover the exact property for the requested app and service. Use both services only when the question needs both. A website and its extension may use different GA properties. Confirm the stream's URL and name. Never substitute a G- measurement ID for the numeric GA property ID. Keep known app identifiers in that app's tracked guidance rather than this shared skill.
Access
Run the requested service's CLI with --version and --help. Use the setup skill for installation, authentication errors or missing property access. Reuse authorized credentials. Report authentication failures separately from empty reports. Do not print credential files, access tokens or refresh tokens.
Use aggregate read commands. The CLIs also expose write commands, but this skill does not authorize them. Do not add or remove properties, submit or delete sitemaps, create audience exports, grant access or change tracking configuration as part of reading telemetry.
Answer the product question
- Choose the reporting interval, metrics and filters needed to answer the question. Discover custom dimensions using
custom-dimsormetadatabefore querying them. - Query a bounded interval for the requested service. Keep dates, time zones, hostname, event filters and reporting identity explicit. Label partial days.
- Query totals separately from breakdowns. User counts across rows can overlap. Do not add distinct users across days, versions or events. Use a real funnel report when sequence matters, rather than dividing unrelated event totals.
- Check the outcome the user asked about: adoption, successful use, saved feedback or search demand. Separate install/update events, title views, filter application and actual scene skips. Request counts, page views and a successful build alone do not prove that a feature works for a viewer.
- Report the source identifiers, requested and returned interval, filters, observed counts, relevant API metadata and the practical conclusion. Distinguish zero, not instrumented, not yet processed and inaccessible. State whether internal/test users were excluded. Do not label all users as external customers when that exclusion is unavailable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 52 lines · 58 tokens per session scan A 95406f431479
google-telemetry is a skill published in the GitHub repository fcakyon/claude-codex-settings (1,211 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,273 once invoked, about $0.0002 per session on Opus 5.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-11-09.
google-telemetry compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| google-telemetryfcakyon/claude-codex-settings | Skill | 1.2k | today | Apache-2.0 | A | 58 | Claude Code |
| github-pr-workflowpaperclipai/paperclip | Skill | 114k | today | MIT | A | 39 | Claude Code, Codex |
| voiceChatCut-Inc/agent-plugin | Skill | 1.0k | 2d ago | Apache-2.0 | A | 124 | Claude Code |
| chatcut-plugin-basics-kimi-workChatCut-Inc/agent-plugin | Skill | 1.0k | 2d ago | Apache-2.0 | A | 152 | Claude Code, Codex |
| chatcut-verification-guideChatCut-Inc/agent-plugin | Skill | 1.0k | 2d ago | Apache-2.0 | A | 31 | Claude Code, Codex |
| githubinitializ/forge | Skill | 230 | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |
| dsh-plugin-publisherlovstudio/skills | Skill | 72 | 4d ago | MIT | A | 82 | Claude Code |