Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/G1Joshi/Agent-Skillsnpx agentmods add skills/g1joshi/agent-skills/gatsbyWrote 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/g1joshi/agent-skills/gatsby)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/gatsby"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/gatsby/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/g1joshi/agent-skills/gatsby"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/gatsby.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.00034 | $0.01260 |
| Opus 5.5 | $0.00014 | $0.00504 |
| Sonnet 5.5 | $0.00007 | $0.00252 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
gatsby 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 26d 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.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gatsby
Gatsby v5 focuses on Valhalla Content Hub and improved build speeds (Slice API). While Next.js has overtaken it, Gatsby remains strong for complex CMS-driven sites.
When to Use
- Static Marketing Websites & Blogs: Pre-rendering React pages with maximum SEO and instantaneous page loads.
- Headless CMS Frontends: Sourcing content from Contentful, Sanity, Strapi, or WordPress via unified GraphQL.
- High-Performance Image Optimization: Delivering responsive WebP/AVIF images with blur-up placeholders.
- Documentation Sites: Generating static documentation with MDX and Algolia search integrations.
Quick Start
// src/pages/index.js
import * as React from "react";
import { Link } from "gatsby";
export default function IndexPage() {
return (
<main>
<h1>Welcome to Gatsby</h1>
<Link to="/about">About Us</Link>
</main>
);
}
export function Head() {
return <title>Home Page</title>;
}
Core Concepts
GraphQL Data Layer & Static Query
Querying build-time metadata and CMS content:
import React from "react";
import { graphql, useStaticQuery, PageProps, Link } from "gatsby";
interface SiteMetaQuery {
site: {
siteMetadata: {
title: string;
description: string;
};
};
}
export default function IndexPage({ data }: PageProps) {
const meta = useStaticQuery<SiteMetaQuery>(graphql`
query SiteTitleQuery {
site {
siteMetadata {
title
description
}
}
}
`);
return (
<main>
<h1>{meta.site.siteMetadata.title}</h1>
<p>{meta.site.siteMetadata.description}</p>
<Link to="/about">About Us</Link>
</main>
);
}
Dynamic Page Creation with gatsby-node.ts
Programmatically generating pages from GraphQL queries at build time:
import path from "path";
import { GatsbyNode } from "gatsby";
export const createPages: GatsbyNode["createPages"] = async ({
graphql,
actions,
}) => {
const { createPage } = actions;
const postTemplate = path.resolve("./src/templates/post.tsx");
const result: any = await graphql(`
query AllArticles {
allMarkdownRemark {
nodes {
frontmatter {
slug
}
}
}
}
`);
result.data.allMarkdownRemark.nodes.forEach((node: any) => {
createPage({
path: `/blog/${node.frontmatter.slug}`,
component: postTemplate,
context: {
slug: node.frontmatter.slug,
},
});
});
};
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.
- 26d ago Changed · +5 lines 5aca22cf0b49
- 1mo ago Changed · +162 lines · +17 tokens per session be453bff40cc
- 1mo ago First seen · 45 lines · 17 tokens per session scan A 0ad973b1f194
gatsby is a skill published in the GitHub repository G1Joshi/Agent-Skills (15 stars, last pushed 26d ago), licensed MIT. It adds 34 tokens to every session and 1,260 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
observability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.