Coastline Realty Blog Writer

Coastline Realty Blog Writer is a skill for Claude Code, Codex from adamshamos/content-skill-generator. It costs 36 tokens per session (1,719 once invoked), scanned A, original, MIT.

A writing guide for Coastline Realty, a San Diego coastal real-estate agency, covering blog posts, neighborhood guides, and buyer or seller articles.

In plain words
What is it for?
Use it to write warm, locally focused content for first-time buyers and families moving within coastal San Diego, with the aim of encouraging a buyer consultation.
Why use it?
It keeps published content consistent in tone, structure, local search terms, and review requirements. It also explains real-estate terms such as escrow, contingency, and HOA for readers who may not know them.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write warm, locally focused content for first-time buyers and families moving within coastal San Diego, with the aim of encouraging a buyer consultation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adamshamos/content-skill-generator/realtor-content-skill
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 adamshamos/content-skill-generator --skill realtor-content-skill
Clone the repo
git clone --depth 1 https://github.com/adamshamos/content-skill-generator

Made for: Claude Code, Codex.

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 Coastline Realty Blog Writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/adamshamos/content-skill-generator/realtor-content-skill/github.svg)](https://agentmods.dev/skills/adamshamos/content-skill-generator/realtor-content-skill)
Your own site
<a href="https://agentmods.dev/skills/adamshamos/content-skill-generator/realtor-content-skill"><img src="https://agentmods.dev/badge/skills/adamshamos/content-skill-generator/realtor-content-skill/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 Coastline Realty Blog Writer

Your own site · 80×15
<a href="https://agentmods.dev/skills/adamshamos/content-skill-generator/realtor-content-skill"><img src="https://agentmods.dev/badge/skills/adamshamos/content-skill-generator/realtor-content-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,719 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.00036 $0.01719
Opus 5 $0.00018 $0.00860
Sonnet 5 $0.00007 $0.00344
Haiku 4.5 $0.00004 $0.00172

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

Security

Grade A, and why

Coastline Realty Blog Writer 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 10d 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.

examples/realtor-content-skill/SKILL.md · 138 lines

How it starts

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

Coastline Realty Blog Writer

When to use this skill

Use whenever writing a blog post, neighborhood guide, or buyer/seller article for Coastline Realty. It defines the voice, structure, SEO rules, and quality bar for all published content.

About Coastline Realty

Coastline Realty is a boutique real-estate agency serving the San Diego coast, helping buyers and sellers navigate the local market with hands-on guidance. Target reader: first-time buyers and move-up families house-hunting in coastal San Diego. Every piece should build trust and get the reader to book a free buyer consultation.

Voice & tone

  • Tone: professional but warm, like a trusted local agent who genuinely likes helping.
  • Use active voice. "We tour the home with you," not "The home is toured."
  • Define any jargon on first use (escrow, contingency, HOA). Prefer plain language.
  • Never give legal, tax, or mortgage-rate advice as fact. Point readers to a licensed professional and avoid guaranteeing prices, timelines, or returns.

Formatting rules

  • One clear idea per paragraph, 2-4 sentences max.
  • Do not use em dashes. Use commas, periods, or restructure the sentence.
  • Avoid contractions in formal posts; a light contraction in a friendly aside is fine.
  • Spelling/locale: American English.
  • Bold the one phrase per section a reader should not miss. Keep bolding sparing.
  • Always refer to the team as "Coastline Realty" or "our team," never "the company."

Content structure (default outline)

Every post follows this shape:

  1. Headline: clear and specific, front-loads the main keyword (e.g., "La Jolla First-Time Buyer Guide").
  2. Intro (1-2 short paragraphs): name the reader's question and what the post delivers. Work the primary keyword into the first paragraph naturally.
  3. Body sections: each under its own subheading, in a logical order.
  4. Conclusion: restate the takeaway in one or two sentences.
  5. Call to action: invite the reader to book a free buyer consultation at coastlinerealty.com/contact.

Read the full file on GitHub · 138 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. 10d ago First seen · 138 lines · 36 tokens per session scan A 60ab15353ad3

Subscribe to this mod's changes

Coastline Realty Blog Writer is a skill published in the GitHub repository adamshamos/content-skill-generator (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,719 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.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens