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.
npx skills add nortonx/ai-tooling-free --skill takeawaysgit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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.
[](https://agentmods.dev/skills/nortonx/ai-tooling-free/takeaways)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/takeaways"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/takeaways/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.
<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/takeaways"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/takeaways.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00045 | $0.00306 |
| Opus 5 | $0.00023 | $0.00153 |
| Sonnet 5 | $0.00009 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
takeaways 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 12d 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.
What it actually says
Arguments
content: The long-form content to extract takeaways from.rating: The product rating or pros/cons rating to group takeaways by.video: The YouTube or Instagram video URL to extract takeaways from.title: (Optional) The title of the video or post caption if not directly extractable from the URL.
Steps
- Extract Content: If a YouTube (video/Shorts) or Instagram (Reels/post) URL is provided, obtain the transcript, caption, or page content. If raw text is provided, use it directly.
- Identify Video Title / Premise: Identify the core question, debate, or promise in the video's title or caption (e.g., "Is X worth it?", "Product A vs Product B", "Does Y really work?").
- Group Key Takeaways: Organize the main findings, pros/cons, key features, or product ratings into a concise comparison.
- Title-Driven Final Verdict: Deliver a direct, unambiguous answer to the title's question or premise. Completely resolve any clickbait or teaser framing by stating the final decision, winner, or result up front.
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.
- 12d ago First seen · 21 lines · 45 tokens per session scan A 41adbb009ce3
takeaways is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 27d ago), licensed MIT. It adds 45 tokens to every session and 306 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
docs-sync
Keep project documentation in sync with code changes. Identifies which docs need updating after a PR merges or code changes, drafts the updates, and manages doc site structure (mkdocs, docusaurus, vitepress). Use when: (1) a PR just merged and docs may need updating, (2) the user says "update the docs" or "sync docs"…
project-planner
Triage ideas, problems, and feature requests into the right format: proposal doc, feature issue, or bug report. Repo-aware — discovers templates and docs structure from the current repository. Use when: (1) the user describes an idea, feature, or problem they want to track, (2) the user says "file a bug", "I have an…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
intuitive-refactor
Refactor and cleanup router for known code/module/API seams, stale surfaces, compatibility shims, architecture cleanup targets, changed-code quality review, oversized modules, repeated cleanup campaigns, and recurring whole-repo architecture maintenance goals. Use this when the user names a concrete seam, wants…
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.