<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resources on Aaron Gabbert</title><link>https://gabbert.me/resources/</link><description>Recent content in Resources on Aaron Gabbert</description><generator>Hugo</generator><language>en-US</language><copyright>© Aaron Gabbert</copyright><atom:link href="https://gabbert.me/resources/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code Config</title><link>https://gabbert.me/resources/claude-code-config/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gabbert.me/resources/claude-code-config/</guid><description>&lt;p&gt;Because sometimes, Googling for these options is difficult.&lt;/p&gt;
&lt;h2 id="links"&gt;Links&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://code.claude.com/docs/en/cli-reference"&gt;CLI Reference&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://code.claude.com/docs/en/settings#available-settings"&gt;&lt;code&gt;settings.json&lt;/code&gt; reference&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://code.claude.com/docs/en/env-vars"&gt;Environment Variables&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://code.claude.com/docs/en/changelog"&gt;Changelog&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="settings-i-find-useful"&gt;Settings I find useful&lt;/h2&gt;
&lt;h3 id="settingsjson"&gt;&lt;code&gt;settings.json&lt;/code&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;respondToBashCommands&lt;/code&gt;: defaults to &lt;code&gt;true&lt;/code&gt; as of &lt;code&gt;2.1.186&lt;/code&gt;. I prefer &lt;code&gt;false&lt;/code&gt;. I do find it useful to run bash commands in the Claude Code terminal for convenience, but if I want the model to respond, I&amp;rsquo;ll send a separate message.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;showClearContextOnPlanAccept&lt;/code&gt;: this used to be the default in Claude Code, and if the plan is sufficiently specific, I find that it can reduce model confusion when executing. However, with Opus/Fable 5, I find that confusion to be less frequent.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Pattern matching tools</title><link>https://gabbert.me/resources/pattern-matching-tools/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gabbert.me/resources/pattern-matching-tools/</guid><description>&lt;p&gt;Pattern matching with various code or no-code tools is a critical skill in the security field. There are countless use cases, so you&amp;rsquo;re likely to come across and have a use for writing one of these patterns.&lt;/p&gt;</description></item><item><title>Publicly available security research tools</title><link>https://gabbert.me/resources/publicly-available-security-research-tools/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gabbert.me/resources/publicly-available-security-research-tools/</guid><description>&lt;p&gt;Below is a list of publicly available resources I have experience with. This list is certainly not exhaustive. Also note that IOCs can be malicious in the absence of hits/reports at these sources. However, they can help you build context while researching or performing analysis.&lt;/p&gt;</description></item></channel></rss>