get-more-from-ai

get-more-from-ai is a skill for Claude Code from mohitagw15856/pm-claude-skills. It costs 140 tokens per session (1,083 once invoked), scanned A, original, MIT.

A guided review of how you currently use AI, followed by a small set of techniques suited to your work. It compares your usual approach with improved examples and gives you a practice plan.

In plain words
What is it for?
It helps improve prompts, add useful context, break large tasks into steps, ask for examples, iterate on drafts, and verify answers.
Why use it?
It addresses weak results caused by vague requests, missing context, accepting the first draft, or failing to check the output. It focuses learning on the habits most relevant to you instead of giving a long general list.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pm-ai-native plugin — 13 skills shipped together

Good fit It helps improve prompts, add useful context, break large tasks into steps, ask for examples, iterate on drafts, and verify answers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mohitagw15856/pm-claude-skills/get-more-from-ai
About the project

PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.

mohitagw15856/pm-claude-skills · 1,449 stars · on GitHub · mohitagw15856.github.io

Install

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.

Any agent
npx skills add mohitagw15856/pm-claude-skills --skill get-more-from-ai
Clone the repo
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills

Made for: Claude Code.

Or install pm-ai-native, the plugin that ships this one along with the rest of its 13 skills.

Wrote 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.

agentmods badge for get-more-from-ai

README.md
[![agentmods](https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/get-more-from-ai/github.svg)](https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/get-more-from-ai)
Your own site
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/get-more-from-ai"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/get-more-from-ai/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.

agentmods 80×15 button for get-more-from-ai

Your own site · 80×15
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/get-more-from-ai"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/get-more-from-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 140 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,083 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00140 $0.01083
Opus 5.5 $0.00056 $0.00433
Sonnet 5.5 $0.00028 $0.00217
Haiku 4.5 $0.00014 $0.00108

Measured 2d ago against content hash c2647f8f7e27, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

get-more-from-ai 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 2d 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.

plugins/pm-ai-native/skills/get-more-from-ai/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Get More From AI

Most people use AI at a fraction of its capability — one-shot questions, accept the first answer, move on — and never learn the handful of techniques that separate a frustrating tool from a force multiplier. The gap isn't a better model; it's how you use the one you have. This reads how you use AI now, picks the two or three techniques that would help you most next, and shows the difference on your own examples — a targeted level-up, not a firehose of a hundred tips.

What This Skill Produces

  • An honest read of your current use — how you use AI now and the specific habits capping your results (one-shot asking, no context, accepting first drafts, no examples)
  • Your highest-leverage next techniques — the 2–3 that would most improve your results, from: giving rich context, iterating instead of accepting, showing examples, decomposing big asks, assigning a role, and verifying output
  • A before/after on your own use — the same task done your current way vs the leveled-up way, so the payoff is concrete
  • A simple practice path — how to build the new techniques into habits one at a time, not all at once
  • The mindset shift — from "search box" to "collaborator you brief, iterate with, and check" — the frame behind all the techniques

Required Inputs

Ask for these if not provided:

  • How you use AI now — a real example of a prompt or task (shows exactly what to level up)
  • Where it frustrates you — where results fall short (points at the missing technique)
  • What you use it for — your main tasks and domains
  • Your level — beginner / regular / trying to go advanced

Framework: Close The Gap One Technique At A Time

  1. Diagnose the current pattern. Look at how the person actually uses AI — the habit capping their results is usually obvious (one-shot, context-starved, first-draft-accepting) and points straight at the fix.
  2. Pick the 2–3 that pay off most. Don't dump every technique. From context-giving, iterating, showing examples, task decomposition, role-setting, and verifying — choose the few that fix this person's bottleneck.
  3. Show the payoff on their example. Take their real task and show it done the leveled-up way beside their current way — the gap is the motivation.
  4. Reframe the mindset. The through-line: AI is a collaborator you brief richly, push back on, and iterate with — not a vending machine you query once. The techniques follow from the frame.
  5. Practice one at a time. Build one technique into a habit before adding the next — layering beats a firehose that nothing sticks from.

Read the full file on GitHub · 64 lines

Changes

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.

  1. 2d ago First seen · 64 lines · 140 tokens per session scan A c2647f8f7e27

Subscribe to this mod's changes

get-more-from-ai is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 1,083 once invoked, about $0.0006 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-10-12.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens