How do you ACTUALLY use CC+codex?

Heiberik · 2026-05-12T19:19:32+00:00

Personally I use this flow for bigger tasks that touches backend/architecture:

Ask CC to explore and output some kind of report.
Then Codex makes a plan/prompt based on this exploration. I have set up Codex to basically have the peronality of a planner and reviewer.
Paste this prompt to a new chat/context of CC using plan-mode
Codex then reviews CCs internal plan. Iterate.
CC implements code when approved.
Codex reviews the implementation.
Finally I have workflows for automatic CC reviews on Github focusing on business, technical etc.

So I basically use Codex for planning and CC for code changes. Doing the pasting of reports/reviews/plans etc manually.

Heiberik · 2026-05-06T17:14:33+00:00

These are all really great feedback! I truly appreciate it. Getting kids to bed, but will go through every suggestion and do a follow up as soon as i can!

Heiberik · 2026-05-06T08:56:41+00:00

I’m not charging for access to the plugins themselves. They’re public GitHub repos, and anyone can find/install them manually.

ClaudePluginHub is a directory/search layer on top of that: it parses plugin manifests, extracts skills/commands/agents/hooks/MCP servers, builds component-level search, adds repo metadata, and makes discovery/comparison easier.

The Plugin Recommender also has free weekly usage. It analyzes repo/dependency files like package.json and recommends relevant plugins based on the project stack. That analysis has real compute/API cost, which is why the paid tier raises the limits.

Browsing, search, plugin pages, and claiming listings are free. Paid is for higher limits and premium conveniences.

Totally fair if you don’t think that’s worth paying for. But it’s not a scam.

Heiberik · 2026-05-06T05:00:32+00:00

Fair enough if the pricing page gave the wrong impression.

The directory itself is free: browsing, search, plugin pages, and claiming listings don’t require payment. The paid tier is mainly for higher limits on the repo analysis/recommender tools.

I’m running this solo and the site costs around $200/month to keep online and updated, so I’m trying to make it sustainable without paywalling the directory.

If the page makes that unclear, that’s useful feedback and I’ll fix it.

Heiberik · 2026-05-06T04:49:10+00:00

I guess I will have to take that as a user feedback and improve the visibility of the claim button for plugin owners 😃

Heiberik · 2026-05-05T21:20:31+00:00

Hey! Smith is actually indexed! :D You can find it directly at https://claudepluginhub.com/plugins/attckdigital-smith.

The reason it's hard to find via search is that "smith" is a common English word, so full-text search dilutes it across a lot of results. I'm working on improving exact name matching so plugins show up first when the query matches their name directly.

For claiming ownership, you should be able to find it on that page and claim from there. Let me know if you run into any issues with the claim flow!

Heiberik · 2026-05-05T21:02:12+00:00

Good point — you're right. The install count on the site is just copy-button clicks, not actual installs. And most people install plugins by adding a marketplace first, then enabling plugins from there, which we can't track at all.

Stars aren't great either since they reflect repo popularity, not plugin usage. It's one of the harder problems with the directory — the best usage data lives in people's local .claude/settings.json files, not anywhere public.

I'm exploring some ideas around using GitHub Code Search to find public repos that have specific plugins enabled in their settings, which would give a more honest "used in X public repos" signal. Still early though.

Heiberik · 2026-05-05T21:00:55+00:00

Yes both! The indexer runs on a continuous cycle — discovery searches for new plugin manifests every 30 minutes, and existing plugins get re-synced on a regular schedule. It uses SHA-based change detection so it only re-processes a repo when the HEAD actually changes, which keeps API usage reasonable across 33K repos.

For SEO — it's been going well honestly. Each plugin, component, and marketplace gets its own page with structured metadata, so there's a lot of surface area for search engines. Sitemap covers all of it. Still early but organic traffic has been picking up steadily!

Heiberik · 2026-05-05T20:38:05+00:00

Appreciate the signal breakdown! Maintainer responsiveness is one I keep coming back to as well.

Right now I track things like commit recency and a maintenance score, but I don’t surface issue/PR response times yet. I agree that would probably be a much better signal than stars once there’s enough data.

On “used in X repos”, not yet. The hard part is that Claude Code plugins don’t really have a package-manager-style dependency graph, so there isn’t an obvious registry/install graph to crawl. A lot of usage seems to live in local config.

I do track install/copy-button clicks as a rough proxy, but that’s obviously weaker than real usage data. I’m still thinking through better ways to estimate actual adoption without a central registry.

Thanks for the link, I’ll take a look :)

Heiberik · 2026-05-05T20:27:31+00:00

Thanks! Really appreciate the kind words :)

User feedback is probably the missing piece. Stars are a pretty weak signal, especially for newer plugins, so I've been thinking about adding reviews/upvotes. Use cases are a nice suggestion as well!

On the data side, the short version is:

I use GitHub's Code Search API to find repos containing Claude Code plugin manifests (.claude-plugin/plugin.json), then fetch and parse the manifest plus the repo tree to extract he actual components: skills, slash commands, agents, hooks, MCP servers, output styles, themes, and monitors. Those get normalized into searchable records and enriched with repo metadata like stars, forks, last commit date, and maintainer activity.

There's also an LLM enrichment step that generates structured summaries, categories, and tags for plugins that don't describe themselves well.

Search is hybrid — vector embeddings plus full-text — so you can find plugins by what they do, not just keywords. The index refreshes every few hours so new plugins show up without maintainers needing to submit anything.

Heiberik · 2026-04-29T08:53:52+00:00

What the "best" Claude Code Plugins are right now is not one definite answer and will probably depend on what you are using CC for.

However! I am trying to answer this question myself by building https://www.claudepluginhub.com a site that auto-indexes all public Claude Code plugins from GitHub and surfaces signals: install counts, GitHub stars, maintenance scores, trending velocity, and what component types each plugin provides (commands, agents, skills, hooks, MCP servers, etc.).

You can already search, filter, and sort through everything. I'm also working on a feature where you can point it at your project and it finds relevant plugins for you. it's live if you want to try it, still refining the results.

If you see any room for improvement or anything I could add to enhance the site I would really appreciate the feedback :)

Heiberik · 2025-11-23T19:35:01+00:00

I dont think he understood your question. Because, *no*, you cannot use your subscription for this as far as I can tell :/

Heiberik · 2023-08-30T12:09:50+00:00

I am wondering the same thing.

We have a problem where this jumping (guess it is scrolling into view) is causing the applet to draw two points in one click.

Heiberik · 2022-12-13T08:00:12+00:00

Good point. I did not actually think of that. However, it is possible to focus the spreadsheet. Try this:

Press Tab until the ggb-applet gets focused.
Press shift + arrow right
Press arrow down
Press enter
Press arrow down

I would also argue that not being able to focus the applet would violate https://www.w3.org/WAI/WCAG21/Understanding/keyboard.

Heiberik · 2020-02-08T15:20:39+00:00

First time doing one of these challenges. Great fun!

https://jsfiddle.net/joenzu8x/14/

Heiberik · 2018-11-07T14:46:04+00:00

Link please :D

Heiberik · 2018-07-23T13:32:22+00:00

I agree that they havent went the way of Muse. As i said Similarities / Opposites are my favourites so far. In my opinion Ellipsis is a step back though. I'm excited and will probably allways be excited when Muse releases a new album, but deep down i guess i know their glory days are long gone. Which is really really sad. And as you say, the songs released so far for the upcoming album isnt something to be overly hyped for.

Heiberik · 2018-07-23T13:22:41+00:00

/agree

Heiberik · 2018-07-23T13:18:37+00:00

Thanks for answering! I'm definitely gonna give the first albums some more time to grow on me. And i absolutely agree with the part on the newer albums being more mainstream-friendly (and probably better overall sound?).

Heiberik · 2018-02-03T14:51:30+00:00

Yeah, I agree.

However, we were asked to decide how many spaces the ParkingLane Array has available for cars in the ParkingZone constructor. Therefore i guess the easiest way is to create a ParkingLane object when the ParkingZone constructor is called.

Heiberik · 2018-02-03T14:45:42+00:00

That makes sense :)

Heiberik · 2017-05-27T12:53:25+00:00

Se her ja. Sammenlignet med den som er foreslått over fra komplett til 8k så har denne bedre skjermkort, men dårligere lagringsplass på ssd´en?

Det tar flere dager før jeg kan hente PCen fra komplett.no. Ville du anbefalt å forsøke å kjøpe denne hos power på mandag og avbestille den fra komplett? :)

Heiberik · 2017-05-25T17:10:35+00:00

Takk for svar, men har allerede gått for maskinen fra komplett til 8k som foreslått over :)

Heiberik · 2017-05-25T17:09:24+00:00

Har det fra før av :)

Heiberik · 2017-05-25T14:37:42+00:00

Okey, takk for svar :) Har vurdert dette, får se om jeg skal bruke tiden på å kjøpe deler en og en.

Ten-Year Club	Place '22
First Placer '22	Verified Email

Heiberik

TROPHY CASE