build-sequential-circuit

build-sequential-circuit is a skill for Claude Code from pjt222/agent-almanac. It costs 84 tokens per session (3,459 once invoked), scanned A, original, MIT.

A method for designing digital logic that remembers previous inputs. It covers storage parts such as latches, flip-flops, registers, and counters, as well as finite state machines that change behavior based on a clock and past events.

In plain words
What is it for?
Use it to build counters, shift registers, registers, sequence detectors, or clocked control systems, and to check their timing and state transitions.
Why use it?
It provides a way to design circuits that count, store values, detect sequences, or follow defined states instead of responding only to the current input.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the agent-almanac plugin — 122 skills, 76 agents shipped together

Good fit Use it to build counters, shift registers, registers, sequence detectors, or clocked control systems, and to check their timing and state transitions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pjt222/agent-almanac/build-sequential-circuit
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 pjt222/agent-almanac --skill build-sequential-circuit
Clone the repo
git clone --depth 1 https://github.com/pjt222/agent-almanac

Made for: Claude Code.

Or install agent-almanac, the plugin that ships this one along with the rest of its 122 skills, 76 agents.

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 build-sequential-circuit

README.md
[![agentmods](https://agentmods.dev/badge/skills/pjt222/agent-almanac/build-sequential-circuit/github.svg)](https://agentmods.dev/skills/pjt222/agent-almanac/build-sequential-circuit)
Your own site
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/build-sequential-circuit"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/build-sequential-circuit/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 build-sequential-circuit

Your own site · 80×15
<a href="https://agentmods.dev/skills/pjt222/agent-almanac/build-sequential-circuit"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/build-sequential-circuit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,459 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Memory Poisoning · line 89
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
  • high Memory Poisoning · line 217
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
  • high Memory Poisoning · line 114
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
How audits are shown
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.00084 $0.03459
Opus 5 $0.00042 $0.01729
Sonnet 5 $0.00017 $0.00692
Haiku 4.5 $0.00008 $0.00346

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

Security

Grade A, and why

build-sequential-circuit 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 5d 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.

i18n/caveman-lite/skills/build-sequential-circuit/SKILL.md · 228 lines

How it starts

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

Build Sequential Circuit

Design a sequential logic circuit by identifying the required memory and state type, constructing a state diagram and transition table, deriving excitation equations for the chosen flip-flop type, implementing the circuit at the gate level using flip-flops and combinational logic, and verifying correctness through timing diagram analysis and state sequence simulation.

When to Use

  • A circuit must remember past inputs or maintain internal state across clock cycles
  • Designing counters (binary, BCD, ring, Johnson), shift registers, or sequence detectors
  • Implementing a finite state machine (Mealy or Moore) from a state diagram or regular expression
  • Adding clocked storage elements to a combinational datapath (registers, pipeline stages)
  • Preparing stateful components for the simulate-cpu-architecture skill (register file, program counter, control FSM)

Inputs

  • Required: Behavioral specification -- one of: state diagram, state table, timing diagram, regular expression to detect, or verbal description of the desired sequential behavior
  • Required: Clock characteristics -- edge-triggered (rising/falling) or level-sensitive; single clock or multi-phase
  • Optional: Flip-flop type preference (D, JK, T, or SR)
  • Optional: Reset type -- synchronous, asynchronous, or none
  • Optional: Maximum state count or bit width constraint
  • Optional: Timing constraints (setup time, hold time, maximum clock frequency)

Procedure

Step 1: Identify Memory and State Requirements

Determine what the circuit needs to remember and how many distinct states it requires:

  1. State enumeration: List all distinct states the circuit must be in. For a sequence detector, each state represents the progress through the target sequence. For a counter, each state is a count value.
  2. State encoding: Choose a binary encoding for the states.
    • Binary encoding: Uses ceil(log2(N)) flip-flops for N states. Minimizes flip-flop count.
    • One-hot encoding: Uses N flip-flops, one per state. Simplifies next-state logic at the cost of more flip-flops.
    • Gray code encoding: Adjacent states differ in exactly one bit. Minimizes transient glitches during transitions.
  3. Input and output classification: Identify primary inputs (external signals), primary outputs, and internal state variables (flip-flop outputs). For Mealy machines, outputs depend on both state and input. For Moore machines, outputs depend only on state.
  4. Flip-flop type selection: Choose based on the design's needs.
    • D flip-flop: Simplest -- next state equals the D input. Best default choice.
    • JK flip-flop: Most flexible -- J=K=1 toggles. Good for counters.
    • T flip-flop: Toggle type -- changes state when T=1. Natural for binary counters.
    • SR latch/flip-flop: Set-Reset -- avoid the S=R=1 condition. Rarely preferred for new designs.

Read the full file on GitHub · 228 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. 5d ago First seen · 228 lines · 84 tokens per session scan A c9fc4fca23d3

Subscribe to this mod's changes

build-sequential-circuit is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 3,459 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

analytics

Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…

yonatangross/orchestkit · 62 tokens

audit-pr

Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".

gtrabanco/agentic-workflow · 71 tokens

design-feature

Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".

gtrabanco/agentic-workflow · 51 tokens

plan-feature

Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".

gtrabanco/agentic-workflow · 66 tokens

product-audit

Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".

gtrabanco/agentic-workflow · 69 tokens

audit-docs

Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…

gtrabanco/agentic-workflow · 188 tokens