fcakyon/claude-codex-settings

COLLECTIONcommunity
fcakyonApache-2.0Updated 4mo 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
4mo agoLast update
Package
Authorfcakyon
LicenseApache-2.0
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
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 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 9 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

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
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in git & code hosting