fcakyon/claude-codex-settings

COLLECTIONcommunity
fcakyonApache-2.0Updated 1mo agoGitHub

My personal Claude Code and OpenAI Codex setup with battle-tested skills, plugins, hooks and agents that I use daily.

My daily battle-tested Claude Code/Desktop and OpenAI Codex setup with skills, commands, hooks, subagents and MCP servers. "They make wrong assumptions on your behalf and just run along with them without checking. They don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs. They really like to overcomplicate code and APIs,…

This collection bundles
56 skills4 agents5 MCP servers18 commands

⚠ The trust score below reflects the collection's repository only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
732GitHub stars
61Forks
1mo agoLast update
Package
Authorfcakyon
LicenseApache-2.0
Sourcegithub
GitHubfcakyon/claude-codex-settings
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—CVE scan · not run+0/30
→ Not yet scanned — package must be on npm
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 19d ago
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

My daily battle-tested Claude Code/Desktop and OpenAI Codex setup with skills, commands, hooks, subagents and MCP servers. "They make wrong assumptions on your behalf and just run along with them without checking. They don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs. They really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves." -- Andrej Karpathy This…

Keywords
ai-agentsai-toolsclaude-aiclaude-codeclaude-code-pluginclaude-skillsclaudecodeclaudecode-configcodexcodex-clicommit-messagecursordokployfrontend-designgemini-cligithubhetznerpluginpull-requestsslackcollection