Skip to main content

Command menu

Jump to a page or search the catalog

Claude Code Prompts: Packs, Hooks and Rules Worth Buying

Claude Code prompts, hooks and rule files: what a usable pack contains, what it costs on Getly, and how to test one on a small repo before you trust it.

8 min read
1,589 words
Claude Code Prompts: Packs, Hooks and Rules Worth Buying

Claude Code prompts are worth buying when they come as a working setup, not a wall of text: a CLAUDE.md template, a few slash commands, hook scripts you can read, and a readme that says where each file goes. A good pack saves you the week of trial and error it takes to make a coding agent follow your project's rules. A weak one is a single text file you could have written in ten minutes. This guide is for the moment before you pay: what a pack should contain, what these packs cost on Getly, what to be careful with, and how to test one on a small repo first.

What the shelf looks like today

We measured the AI prompts and AI data shelves on Getly on 6 November 2026. The part that matters for this article is the narrow slice: listings whose name contains "claude" or "cursor". There are 60 of them. None is free. The middle half costs between $2.99 and $9.99, and the median is $4.99. So a Claude Code or Cursor pack is a small purchase, cheaper than one hour of a developer's time almost anywhere.

Licences in that slice lean personal: 45.0% of these listings are for personal use only, 31.7% allow commercial use, and 23.3% state no licence at all. That last group is where you should send the seller a message before you buy, especially if the files will live in a company repository.

For context, the whole shelf (both categories, every kind of prompt and AI dataset) holds 704 listings. 4.3% of them are free, the median price is $5.99 and the middle half sits between $4.99 and $12.00. A third of the whole shelf (33.8%) states no licence.

Measured 6 November 2026Claude and Cursor listingsWhole AI prompts and AI data shelf
Listings60704
Free0%4.3%
Middle half of prices$2.99 to $9.99$4.99 to $12.00
Median price$4.99$5.99
Personal use only45.0%22.4%
Commercial use allowed31.7%41.8%
No licence stated23.3%33.8%

What a usable Claude Code pack contains

Claude Code reads its instructions from plain files in your project. That is good news for buyers: you can open every file before you use it, and you can see exactly what changed in your repo afterwards. A pack that respects this is built from the same pieces the tool itself uses.

  • A CLAUDE.md template. This is the project memory file at the root of the repo. A useful template has sections you fill in: how to build, how to run tests, code style, what not to touch, and how to commit. It should be short. A CLAUDE.md that runs to many screens gets read less carefully, by the agent and by your team.
  • Custom slash commands. Markdown files in .claude/commands, one per task: review a diff, write a test for a function, prepare a release note. Each should say what it does in its first line and take an argument where it makes sense.
  • Skills. Folders in .claude/skills, each with a SKILL.md that explains when to use it and what steps to follow, plus any helper files. Good skills are narrow: "write a database migration the way this project does it", not "be a senior engineer".
  • Subagent definitions. Optional. A reviewer or test-writer agent with its own short instructions can keep the main session focused. A pack should explain why each one exists.
  • Hook scripts. Hooks run shell commands on events, for example before or after a tool call, and are configured in settings.json. Typical useful hooks run a formatter after an edit, or block edits to a folder you name. They are also the part that needs the most care (see below).
  • Rule files for other agents. Many packs also ship Cursor rules or similar files, so the same conventions work in more than one editor. Check that the listing says which tools are covered.
  • Examples and a readme. A worked example on a small sample project, and a readme that says which file goes where, in what order, and how to remove it again. Without a readme you are reverse-engineering someone else's setup.

Prompt-only packs have their place. A PDF or text file of well-tested prompts for code review, refactoring or writing tests can be worth a few dollars. Just know what you are buying: words to paste, not a configuration that changes how the agent behaves in your repo.

Packs and shelves on Getly worth a look

Two listings in the Claude slice show the range of what is on offer. Prices are as listed on 6 November 2026.

ListingFormatPrice
Claude GuideText file$20
Claude Opus 4.6 Power ModeText file$1

Both ship as text files, so read the description and the file list on the product page to see what exactly is inside before you pay. If the description does not say whether it covers Claude Code in the terminal, the chat app or both, ask the seller. For a wider choice, browse AI Prompts, and for datasets and other AI material see AI Data. Use the search box with "claude code", "cursor rules" or "hooks" to narrow it down.

Red flags before you pay

  • Claims about model internals. Nobody selling a prompt can switch on a hidden mode, unlock a bigger model or remove limits. A prompt changes instructions, nothing else. A listing that promises more than that is selling a story.
  • "Jailbreak" wording. Prompts built to get around the model's rules are not a productivity tool. In a work repo they are a liability.
  • Hooks you cannot read. A hook is a shell command that runs on your machine with your permissions. Compiled binaries, minified scripts or a hook that downloads something from the internet should be a hard no.
  • Secrets in the files. If a settings file contains an API key, a token or a path to someone else's machine, the seller did not clean up. Do not use those values, and be wary of the rest.
  • No version or date. Coding agents change often. A pack should say which version or month it was written for, so you know how fresh the commands are.
  • Blanket permissions. A settings.json that allows every command without asking saves clicks and removes the one check you have. Prefer packs that allow a short, named list.

How to test a pack on a small repo first

Never drop a new pack straight into the project you care about. Fifteen minutes on a throwaway repo tells you more than the description does.

  1. Make a small test repo. A copy of a tiny project, or a new folder with a few files and a test. Run git init and commit, so you have a clean starting point.
  2. Read every file in the pack. Start with settings.json and every hook script. If you cannot tell what a line does, look it up or leave it out.
  3. Copy files in one group at a time. First the CLAUDE.md, then the commands, then skills, hooks last. Commit after each group.
  4. Run the same task twice. Ask for the same small change with and without the pack. Compare the results with git diff. You are looking for fewer corrections from you, not longer output.
  5. Check what hooks actually did. After a session, run git status and look for files you did not expect to change.
  6. Revert freely. If something misbehaves, git checkout or git reset back to your last commit. That is why you committed.
  7. Only then move it into your real project, adapting the CLAUDE.md to your build, tests and rules.

If the pack fails this test, you have a short refund conversation, not a broken repository.

Licence: personal or commercial

A prompt pack is text, and text is easy to copy into a shared repo. That is exactly where the licence starts to matter. Personal use is fine for your own projects. Once the files go into a company repository that colleagues use, or into client work, you want a listing that allows commercial use. In the Claude and Cursor slice, fewer than a third of listings say so (31.7%), so check the licence line on the product page next to the buy button. When a listing states no licence, the page shows nothing rather than guessing. In that case message the seller through Getly and ask before you buy.

Also check whether the pack may be adapted. Almost everyone edits a CLAUDE.md template, so a licence that forbids changes is not practical.

Paying and downloading on Getly

You can pay by card, with Apple Pay or Google Pay where your device supports it, or with USDT or USDC stablecoins. PayPal is not accepted. You do not need an account to buy: the receipt email carries a download link for every file. Card orders deliver right after payment, crypto orders once the network confirms it. Your purchase stays in your library and does not expire, so you can come back for an updated version of the files later.

Every purchase has a refund window of at least 30 days. A refund request is reviewed by the Getly team, not decided by the seller. If a pack ships as a PDF of ten pages or more, the product page shows a watermarked excerpt, so you can read a few pages before paying. For anything else, ask the seller: a good one will tell you which tools and versions the files were tested with.

Ready to start selling?

Independent marketplace for digital creators. Keep 80–90% of every sale. Accept cards and stablecoins.